/ 
Mojolicious-0.999931
⭐ Starred 2674 / Mojolicious::Plugins
Security Advisories (12)
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-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.

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

Mojolicious::Plugins - Plugins

SYNOPSIS

use Mojolicious::Plugins;

DESCRIPTION

Mojolicous::Plugins is the plugin manager of Mojolicious. In your application you will usually use it to load plugins. To implement your own plugins see Mojolicious::Plugin and the add_hook method below.

ATTRIBUTES

Mojolicious::Plugins implements the following attributes.

hooks

my $hooks = $plugins->hooks;
$plugins  = $plugins->hooks({foo => [sub {...}]});

Hash reference containing all hooks that have been registered by loaded plugins.

namespaces

my $namespaces = $plugins->namespaces;
$plugins       = $plugins->namespaces(['Mojolicious::Plugin']);

Namespaces to load plugins from. You can add more namespaces to load application specific plugins.

METHODS

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

add_hook

$plugins = $plugins->add_hook(event => sub {...});

Hook into an event. The following events are available and run in the listed order.

after_build_tx

Runs right after the transaction is built and before the HTTP request gets parsed. One usage case would be upload progress bars. (Passed the transaction instance)

$plugins->add_hook(before_request => sub {
    my ($self, $tx) = @_;
});
before_dispatch

Runs before the dispatchers determines what action to run. (Passed the default controller instance)

$plugins->add_hook(before_dispatch => sub {
    my ($self, $c) = @_;
});
after_static_dispatch

Runs after the static dispatcher determines if a static file should be served. (Passed the default controller instance) Note that the callbacks of this hook run in reverse order.

$plugins->add_hook(after_static_dispatch => sub {
    my ($self, $c) = @_;
});
after_dispatch

Runs after the dispatchers determines what action to run. (Passed the default controller instance) Note that the callbacks of this hook run in reverse order.

$plugins->add_hook(after_dispatch => sub {
    my ($self, $c) = @_;
});

You could also add custom events by using run_hook and run_hook_reverse in your application.

load_plugin

my $plugin = $plugins->load_plugin('something');
my $plugin = $plugins->load_plugin('Foo::Bar');

Load a plugin from the configured namespaces or by full module name. Note that this method is EXPERIMENTAL and might change without warning!

register_plugin

$plugins->register_plugin('something', $app);
$plugins->register_plugin('something', $app, foo => 23);
$plugins->register_plugin('something', $app, {foo => 23});
$plugins->register_plugin('Foo::Bar', $app);
$plugins->register_plugin('Foo::Bar', $app, foo => 23);
$plugins->register_plugin('Foo::Bar', $app, {foo => 23});

Load a plugin from the configured namespaces or by full module name and run register. Optional arguments are passed to register. Note that this method is EXPERIMENTAL and might change without warning!

run_hook

$plugins = $plugins->run_hook('foo');
$plugins = $plugins->run_hook(foo => 123);

Runs a hook.

run_hook_reverse

$plugins = $plugins->run_hook_reverse('foo');
$plugins = $plugins->run_hook_reverse(foo => 123);

Runs a hook in reverse order.

SEE ALSO

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