/ 
Plack-1.0021
⭐ Starred 488
/ Plack::App::CGIBin
Security Advisories (3)
CPANSA-Plack-2015-0202 (2015-02-02)

Fixed a possible directory traversal with Plack::App::File on Win32.

CPANSA-Plack-2014-0801 (2014-08-01)

Plack::App::File would previously strip trailing slashes off provided paths. This in combination with the common pattern of serving files with Plack::Middleware::Static could allow an attacker to bypass a whitelist of generated files

CVE-2026-7381 (2026-04-29)

Plack::Middleware::XSendfile versions through 1.0053 for Perl can allow client-controlled path rewriting. Plack::Middleware::XSendfile allows the variation setting (sendfile type) to be set by the client via the X-Sendfile-Type header, if it is not considered in the middleware constructor or the Plack environment. A malicious client can set the X-Sendfile-Type header to "X-Accel-Redirect" to services running behind nginx reverse proxies, and then set the X-Accel-Mapping to map the path to an arbitrary file on the server. Since 1.0053, Plack::Middleware::XSendfile is deprecated and will be removed from future releases of Plack. This is similar to CVE-2025-61780 for Rack::Sendfile, although Plack::Middleware::XSendfile has some mitigations that disallow regular expressions to be used in the mapping, and only apply the mapping for the "X-Accel-Redirect" type.

NAME

Plack::App::CGIBin - cgi-bin replacement for Plack servers

SYNOPSIS

use Plack::App::CGIBin;
use Plack::Builder;

my $app = Plack::App::CGIBin->new(root => "/path/to/cgi-bin")->to_app;
builder {
    mount "/cgi-bin" => $app;
};

# Or from the command line
plackup -MPlack::App::CGIBin -e 'Plack::App::CGIBin->new(root => "/path/to/cgi-bin")->to_app'

DESCRIPTION

Plack::App::CGIBin allows you to load CGI scripts from a directory and convert them into a PSGI application.

This would give you the extreme easiness when you have bunch of old CGI scripts that is loaded using cgi-bin of Apache web server.

HOW IT WORKS

This application checks if a given file path is a perl script and if so, uses CGI::Compile to compile a CGI script into a sub (like ModPerl::Registry) and then run it as a persistent application using CGI::Emulate::PSGI.

If the given file is not a perl script, it executes the script just like a normal CGI script with fork & exec. This is like a normal web server mode and no performance benefit is achieved.

The default mechanism to determine if a given file is a Perl script is as follows:

  • Check if the filename ends with .pl. If yes, it is a Perl script.

  • Open the file and see if the shebang (first line of the file) contains the word perl (like #!/usr/bin/perl). If yes, it is a Perl script.

You can customize this behavior by passing exec_cb callback, which takes a file path to its first argument.

For example, if your perl-based CGI script uses lots of global variables and such and are not ready to run on a persistent environment, you can do:

my $app = Plack::App::CGIBin->new(
    root => "/path/to/cgi-bin",
    exec_cb => sub { 1 },
)->to_app;

to always force the execute option for any files.

AUTHOR

Tatsuhiko Miyagawa

SEE ALSO

Plack::App::File CGI::Emulate::PSGI CGI::Compile Plack::App::WrapCGI

See also Plack::App::WrapCGI if you compile one CGI script into a PSGI application without serving CGI scripts from a directory, to remove overhead of filesystem lookups, etc.