How severe is CVE-2011-0049?

No CVSS score has been assigned to CVE-2011-0049 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2011-0049?

Affected package information for CVE-2011-0049 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2011-0049?

No fixed release is recorded for CVE-2011-0049 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2011-0049 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2011-0049 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2011-0049 actively exploited in the wild?

Yes. There are 5 known exploit references for CVE-2011-0049, including 1 documented proof-of-concept exploit on Exploit-DB and 4 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2011-0049?

CVE-2011-0049 has an EPSS (Exploit Prediction Scoring System) score of 95.4%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2011-0049?

CVE-2011-0049 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2011-0049?

A Nuclei detection template exists for CVE-2011-0049, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2011-0049 published, and has it been updated?

CVE-2011-0049 was published on February 4, 2011 and was last updated on August 6, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2011-0049 — Mozilla

CVE-2011-0049 is a Path Traversal vulnerability. 5 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

Directory traversal vulnerability in the _list_file_get function in lib/Majordomo.pm in Majordomo 2 before 20110131 allows remote attackers to read arbitrary files via .. (dot dot)…

Published

Feb 4, 2011

Updated

Aug 6, 2024

Affected

1 product

Patched

See advisory

Exploits

5 known

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

95.4%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

Directory traversal vulnerability in the _list_file_get function in lib/Majordomo.pm in Majordomo 2 before 20110131 allows remote attackers to read arbitrary files via .. (dot dot) sequences in the help command, as demonstrated using (1) a crafted email and (2) cgi-bin/mj_wwwusr in the web interface.

Affected Products

1 product · 30 configurations

Application

majordomo 2mj2

≤ 20110130

29 versions

201101012011010220110103201101042011010520110106201101072011010820110109201101102011011120110112

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-16103remotemultiple✓ Verified

Majordomo2 - 'SMTP/HTTP' Directory Traversal

by Michael Brooks · Feb 3, 2011

Exploit-DB Source

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2011-0049 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

How to detect CVE-2011-0049

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2011-0049 -u https://target

Template: Majordomo2 - SMTP/HTTP Directory Traversal
Severity: medium
Impact: This vulnerability can lead to unauthorized access to sensitive files and data on the server.
Remediation: Upgrade to the latest version to mitigate this vulnerability.

Template by ProjectDiscovery nuclei-templates (pikpikcu), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2011-0049 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works