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.

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

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

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

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

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-2010-4803 (2011-05-03)

Mojolicious before 0.999927 does not properly implement HMAC-MD5 checksums, which has unspecified impact and remote attack vectors.

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.

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

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-2026-14803 (2026-07-06)

Mojo::JSON versions before 9.47 for Perl allow memory exhaustion via unbounded recursion in the pure-Perl decoder. The pure-Perl decode path (`_decode_value` dispatching to `_decode_array` and `_decode_object`) recurses with no depth limit, so a small deeply nested JSON document can consume excessive memory. This path is the default when Cpanel::JSON::XS is not installed or `MOJO_NO_JSON_XS=1` is set; the Cpanel::JSON::XS fast path is not affected. Any caller that decodes an untrusted JSON body, for example `Mojo::Message::json` reached through `$c->req->json`, can exhaust process memory and cause denial of service.

NAME

Mojo - The Box!

SYNOPSIS

use base 'Mojo';

# All the complexities of CGI, FastCGI, PSGI, HTTP and WebSocket get
# reduced to a single method call!
sub handler {
    my ($self, $tx) = @_;

    # Request
    my $method = $tx->req->method;
    my $path   = $tx->req->url->path;

    # Response
    $tx->res->headers->content_type('text/plain');
    $tx->res->body("$method request for $path!");
}

DESCRIPTION

Mojo provides a flexible runtime environment for Perl web frameworks. It provides all the basic tools and helpers needed to write simple web applications and higher level web frameworks such as Mojolicious.

See Mojolicious for more!

ATTRIBUTES

Mojo implements the following attributes.

build_tx_cb

my $cb = $mojo->build_tx_cb;
$mojo  = $mojo->build_tx_cb(sub { ... });

The transaction builder callback, by default it builds a Mojo::Transaction::HTTP object.

client

my $client = $mojo->client;
$mojo      = $mojo->client(Mojo::Client->new);

A full featured HTTP 1.1 client for use in your applications, by default a Mojo::Client object.

home

my $home = $mojo->home;
$mojo    = $mojo->home(Mojo::Home->new);

The home directory of your application, by default a Mojo::Home object which stringifies to the actual path.

log

my $log = $mojo->log;
$mojo   = $mojo->log(Mojo::Log->new);

The logging layer of your application, by default a Mojo::Log object.

websocket_handshake_cb

my $cb = $mojo->websocket_handshake_cb;
$mojo  = $mojo->websocket_handshake_cb(sub { ... });

The websocket handshake callback, by default it builds a Mojo::Transaction::WebSocket object and handles the response for the handshake request.

METHODS

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

new

my $mojo = Mojo->new;

Construct a new Mojo application. Will automatically detect your home directory and set up logging to log/mojo.log if there's a log directory.

handler

$tx = $mojo->handler($tx);

The handler is the main entry point to your application or framework and will be called for each new transaction.

sub handler {
    my ($self, $tx) = @_;
}

start

Mojo->start;
Mojo->start('daemon');

Start the Mojo::Commands command line interface for your application.

SEE ALSO

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