Security Advisories (13)
CPANSA-Mojolicious-2022-03 (2022-12-10)

Mojo::DOM did not correctly parse <script> tags.

CPANSA-Mojolicious-2021-02 (2021-06-01)

Small sessions could be used as part of a brute-force attack to decode the session secret.

CVE-2021-47208 (2021-03-16)

A bug in format detection can potentially be exploited for a DoS attack.

CVE-2018-25100 (2018-02-13)

Mojo::UserAgent::CookieJar leaks old cookies because of the missing host_only flag on empty domain.

CPANSA-Mojolicious-2015-01 (2015-02-02)

Directory traversal on Windows

CVE-2010-4802 (2011-05-03)

Commands.pm in Mojolicious before 0.999928 does not properly perform CGI environment detection, which has unspecified impact and remote attack vectors.

CPANSA-Mojolicious-2018-03 (2018-05-19)

Mojo::UserAgent was not checking peer SSL certificates by default.

CPANSA-Mojolicious-2018-02 (2018-05-11)

GET requests with embedded backslashes can be used to access local files on Windows hosts

CPANSA-Mojolicious-2014-01 (2014-10-07)

Context sensitivity of method param could lead to parameter injection attacks.

CVE-2011-1841 (2011-03-10)

Mojolicious is vulnerable to cross-site scripting, caused by improper validation of user-supplied input by link_to helper. A remote attacker could exploit this vulnerability using a specially-crafted URL to execute script in a victim's Web browser within the security context of the hosting Web site, once the URL is clicked. An attacker could use this vulnerability to steal the victim's cookie-based authentication credentials.

CVE-2011-1589 (2011-04-05)

Directory traversal vulnerability in Path.pm in Mojolicious before 1.16 allows remote attackers to read arbitrary files via a %2f..%2f (encoded slash dot dot slash) in a URI.

CVE-2011-1841 (2011-05-03)

Cross-site scripting (XSS) vulnerability in the link_to helper in Mojolicious before 1.12 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.

CVE-2024-58134 (2025-05-03)

Mojolicious versions from 0.999922 for Perl uses a hard coded string, or the application's class name, as an HMAC session cookie secret by default. These predictable default secrets can be exploited by an attacker to forge session cookies.  An attacker who knows or guesses the secret could compute valid HMAC signatures for the session cookie, allowing them to tamper with or hijack another user’s session.

NAME

Mojo::Server - HTTP Server Base Class

SYNOPSIS

use base 'Mojo::Server';

sub run {
    my $self = shift;

    # Get a transaction
    my $tx = $self->build_tx_cb->($self);

    # Call the handler
    $tx = $self->handler_cb->($self);
}

DESCRIPTION

Mojo::Server is an abstract HTTP server base class.

ATTRIBUTES

Mojo::Server implements the following attributes.

app

my $app = $server->app;
$server = $server->app(MojoSubclass->new);

Application this server handles, defaults to a Mojo::HelloWorld object.

app_class

my $app_class = $server->app_class;
$server       = $server->app_class('MojoSubclass');

Class of the application this server handles, defaults to Mojo::HelloWorld.

build_tx_cb

my $btx = $server->build_tx_cb;
$server = $server->build_tx_cb(sub {
    my $self = shift;
    return Mojo::Transaction::HTTP->new;
});

Transaction builder callback.

handler_cb

my $handler = $server->handler_cb;
$server     = $server->handler_cb(sub {
    my ($self, $tx) = @_;
});

Handler callback.

reload

my $reload = $server->reload;
$server    = $server->reload(1);

Activate automatic reloading.

websocket_handshake_cb

my $handshake = $server->websocket_handshake_cb;
$server       = $server->websocket_handshake_cb(sub {
    my ($self, $tx) = @_;
});

WebSocket handshake callback.

METHODS

Mojo::Server inherits all methods from Mojo::Base and implements the following new ones.

run

$server->run;

Start server.

SEE ALSO

Mojolicious, Mojolicious::Guides, http://mojolicious.org.