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 products 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 patch CVE-2011-0049?

No patch has shipped for CVE-2011-0049 yet — track the mj2 majordomo 2 advisory for a fixed release and apply the workarounds below in the meantime.

How do I detect CVE-2011-0049 across my infrastructure?

Inventory every mj2 majordomo 2 deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

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

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2011-0049?

O3 detects and blocks CVE-2011-0049 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

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.

Which products and versions are affected by CVE-2011-0049?

CVE-2011-0049 affects mj2 majordomo 2 (29 versions, e.g. 20110101, 20110102, 20110103…). Check the affected-products list on this page against your deployed version to confirm 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 June 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2011-0049

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

Jun 16, 2026

Affected

0 pkgs

Patched

None yet

Exploits

5 known

EPSS Exploitation Probability

via FIRST.org ↗

95.4%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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

Vendor / appliance

Detect
Inventory every mj2 majordomo 2 deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Remediation status
No patch has shipped for CVE-2011-0049 yet — track the mj2 majordomo 2 advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2011-0049 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2011-0049. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2011-0049 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2011-0049 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works

CVE-2011-0049

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

How O3 protects you

Frequently Asked Questions

Is CVE-2011-0049 being exploited in your environment?