Security Advisories (14)
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-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-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-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.

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.

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

Test::Mojo - Testing Mojo!

SYNOPSIS

use Test::Mojo;
my $t = Test::Mojo->new(app => 'MyApp');

$t->get_ok('/welcome')
  ->status_is(200)
  ->content_like(qr/Hello!/, 'welcome message!');

$t->post_form_ok('/search', {title => 'Perl', author => 'taro'})
  ->status_is(200)
  ->content_like(qr/Perl.+taro/);

$t->delete_ok('/something')
  ->status_is(200)
  ->header_is('X-Powered-By' => 'Mojolicious (Perl)')
  ->content_is('Hello world!');

DESCRIPTION

Test::Mojo is a collection of testing helpers for everyone developing Mojo and Mojolicious applications.

ATTRIBUTES

Test::Mojo implements the following attributes.

app

my $app = $t->app;
$t      = $t->app(MyApp->new);

Application to be tested.

client

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

Client used for testing.

redirects

my $redirects = $t->redirects;
$t            = $t->redirects([]);

History of redirected requests.

tx

my $tx = $t->tx;
$t     = $t->tx(Mojo::Transaction::Simple->new);

Current transaction.

max_redirects

my $max_redirects = $t->max_redirects;
$t                = $t->max_redirects(3);

Maximum number of redirects, defaults to 0.

METHODS

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

content_is

$t = $t->content_is('working!');
$t = $t->content_is('working!', 'right content!');

Check response content for exact match.

content_like

$t = $t->content_like(qr/working!/);
$t = $t->content_like(qr/working!/, 'right content!');

Check response content for similar match.

content_type_is

$t = $t->content_type_is('text/html');
$t = $t->content_type_is('text/html', 'right content type!');

Check response content type for exact match.

content_type_like

$t = $t->content_type_like(qr/text/);
$t = $t->content_type_like(qr/text/, 'right content type!');

Check response content type for similar match.

delete_ok

$t = $t->delete_ok('/foo');
$t = $t->delete_ok('/foo', {Expect => '100-continue'});
$t = $t->delete_ok('/foo', 'Hi there!');
$t = $t->delete_ok('/foo', {Expect => '100-continue'}, 'Hi there!');
$t = $t->delete_ok(
   '/foo',
   {Expect => '100-continue'},
   'Hi there!',
   'request worked!'
);

Perform a DELETE request.

get_ok

$t = $t->get_ok('/foo');
$t = $t->get_ok('/foo', {Expect => '100-continue'});
$t = $t->get_ok('/foo', 'Hi there!');
$t = $t->get_ok('/foo', {Expect => '100-continue'}, 'Hi there!');
$t = $t->get_ok(
    '/foo',
    {Expect => '100-continue'},
    'Hi there!',
    'request worked!'
);

Perform a GET request.

head_ok

$t = $t->head_ok('/foo');
$t = $t->head_ok('/foo', {Expect => '100-continue'});
$t = $t->head_ok('/foo', 'Hi there!');
$t = $t->head_ok('/foo', {Expect => '100-continue'}, 'Hi there!');
$t = $t->head_ok(
    '/foo',
    {Expect => '100-continue'},
    'Hi there!',
    'request worked!'
);

Perform a HEAD request.

header_is

$t = $t->header_is(Expect => '100-continue');
$t = $t->header_is(Expect => '100-continue', 'right header!');

Check response header for exact match.

header_like

$t = $t->header_like(Expect => qr/100-continue/);
$t = $t->header_like(Expect => qr/100-continue/, 'right header!');

Check response header for similar match.

json_content_is

$t = $t->json_content_is([1, 2, 3]);
$t = $t->json_content_is([1, 2, 3], 'right content!');

Check response content for JSON data.

post_ok

$t = $t->post_ok('/foo');
$t = $t->post_ok('/foo', {Expect => '100-continue'});
$t = $t->post_ok('/foo', 'Hi there!');
$t = $t->post_ok('/foo', {Expect => '100-continue'}, 'Hi there!');
$t = $t->post_ok('/foo', 'Hi there!', 'request worked!');
$t = $t->post_ok(
    '/foo',
    {Expect => '100-continue'},
    'Hi there!',
    'request worked!'
);

Perform a POST request.

post_form_ok

$t = $t->post_form_ok('/foo' => {test => 123});
$t = $t->post_form_ok('/foo' => 'UTF-8' => {test => 123});
$t = $t->post_form_ok('/foo', {test => 123}, {Expect => '100-continue'});
$t = $t->post_form_ok(
    '/foo',
    'UTF-8',
    {test => 123},
    {Expect => '100-continue'}
);
$t = $t->post_form_ok('/foo', {test => 123}, 'Hi there!');
$t = $t->post_form_ok('/foo', 'UTF-8', {test => 123}, 'Hi there!');
$t = $t->post_form_ok(
    '/foo',
    {test   => 123},
    {Expect => '100-continue'},
    'Hi there!'
);
$t = $t->post_form_ok(
    '/foo',
    'UTF-8',
    {test   => 123},
    {Expect => '100-continue'},
    'Hi there!'
);

Submit a POST form.

put_ok

$t = $t->put_ok('/foo');
$t = $t->put_ok('/foo', {Expect => '100-continue'});
$t = $t->put_ok('/foo', 'Hi there!');
$t = $t->put_ok('/foo', {Expect => '100-continue'}, 'Hi there!');
$t = $t->put_ok(
    '/foo',
    {Expect => '100-continue'},
    'Hi there!',
    'request worked!'
);

Perform a PUT request.

reset_session

$t = $t->reset_session;

Reset user agent session.

status_is

$t = $t->status_is(200);
$t = $t->status_is(200, 'right status!');

Check response status for exact match.

SEE ALSO

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