How severe is CVE-2024-49771?

CVE-2024-49771 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2024-49771?

CVE-2024-49771 affects the following packages: net.sf.mpxj:mpxj (Maven), net.sf.mpxj (NuGet), net.sf.mpxj-for-csharp (NuGet), net.sf.mpxj-for-vb (NuGet), MPXJ.Net (NuGet), mpxj (PyPI), mpxj (RubyGems). Ecosystems affected: Maven, NuGet, PyPI, RubyGems.

How do I fix CVE-2024-49771?

Update net.sf.mpxj:mpxj to 13.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-49771 is resolved across your whole dependency graph.

How do I detect CVE-2024-49771 in my Maven, NuGet, PyPI, RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.sf.mpxj:mpxj. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2024-49771?

O3 pinpoints whether CVE-2024-49771 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2024-49771 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-49771 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-49771?

CVE-2024-49771 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 37th 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. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2024-49771 published, and has it been updated?

CVE-2024-49771 was published on October 28, 2024 and was last updated on April 10, 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-2024-49771: MPXJ has a Potential Path Traversal Vulnerabili…

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk37th percentile+0.22%

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.

Blast Radius

7 pkgs affected

☕net.sf.mpxj:mpxj.NETnet.sf.mpxj.NETnet.sf.mpxj-for-csharp.NETnet.sf.mpxj-for-vb.NETMPXJ.Net🐍mpxj💎mpxj

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven, NuGet packages — download data is not available via public APIs for these ecosystems.

Description

MPXJ is an open source library to read and write project plans from a variety of file formats and databases. The patch for the historical vulnerability CVE-2020-35460 in MPXJ is incomplete as there is still a possibility that a malicious path could be constructed which would not be picked up by the original fix and allow files to be written to arbitrary locations. The issue is addressed in MPXJ version 13.5.1.

Affected Packages

7 total 7 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`net.sf.mpxj:mpxj`	≥ 8.3.5&&< 13.5.1	13.5.1
.NETNuGet	`net.sf.mpxj`	≥ 8.3.5&&< 13.5.1	13.5.1
.NETNuGet	`net.sf.mpxj-for-csharp`	≥ 8.3.5&&< 13.5.1	13.5.1
.NETNuGet	`net.sf.mpxj-for-vb`	≥ 8.3.5&&< 13.5.1	13.5.1
.NETNuGet	`MPXJ.Net`	≥ 13.0.0&&< 13.5.1	13.5.1
🐍PyPI	`mpxj`	≥ 8.3.5&&< 13.5.1	13.5.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.sf.mpxj:mpxj. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update net.sf.mpxj:mpxj to 13.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-49771 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2024-49771 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

Frequently Asked Questions

MPXJ is an open source library to read and write project plans from a variety of file formats and databases. The patch for the historical vulnerability CVE-2020-35460 in MPXJ is incomplete as there is still a possibility that a malicious path could be constructed which would not be picked up by the original fix and allow files to be written to arbitrary locations. The issue is addressed in MPXJ version 13.5.1.

O3 Security · Impact-Aware SCA

Is CVE-2024-49771 in your dependencies?

O3 detects CVE-2024-49771 across Maven, NuGet, PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

CVE-2024-49771