MediumGHSA-j945-c44v-97g6CVE-2024-49771PYSEC-2026-1681

MPXJ has a Potential Path Traversal Vulnerability

Published 28 Oct 2024 · Updated 7 Jul 2026

Is your project on an affected net.sf.mpxj:mpxj?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=8.3.5 <13.5.1
Fixed in
13.5.1
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=net.sf.mpxj:mpxj -DdepVersion=13.5.1 -DforceVersion=true
mpxjRubyGems
Affected
>=8.3.5 <13.5.1
Fixed in
13.5.1
Update to the fixed version for your release line, for example:bundle update --conservative mpxj # Gemfile: '>= 13.5.1'
mpxjPyPI
Affected
>=8.3.5 <13.5.1
Fixed in
13.5.1
Update to the fixed version for your release line, for example:pip install 'mpxj>=13.5.1'
Affected
>=8.3.5 <13.5.1
Fixed in
13.5.1
Update to the fixed version for your release line, for example:dotnet add package net.sf.mpxj --version 13.5.1
Affected
>=8.3.5 <13.5.1
Fixed in
13.5.1
Update to the fixed version for your release line, for example:dotnet add package net.sf.mpxj-for-csharp --version 13.5.1
Affected
>=8.3.5 <13.5.1
Fixed in
13.5.1
Update to the fixed version for your release line, for example:dotnet add package net.sf.mpxj-for-vb --version 13.5.1
Affected
>=13.0.0 <13.5.1
Fixed in
13.5.1
Update to the fixed version for your release line, for example:dotnet add package MPXJ.Net --version 13.5.1

Details

Impact

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.

Patches

The issue is addressed in MPXJ version 13.5.1

Workarounds

Do not pass zip files to MPXJ.

References

N/A

Credits

Issue report and patch provided by yyjLF and sprinkle

Is GHSA-j945-c44v-97g6 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected net.sf.mpxj:mpxj, and gives you the command that fixes it.

More advisories for net.sf.mpxj:mpxj

  • MediumCVE-2026-65829MPXJ: Potential Path Traversal Vulnerability in Primavera P3 PRX and SureTrak STX readers · 22 Sept 2026
  • HighCVE-2026-61570MPXJ: XXE Vulnerability in MerlinReader · 22 Sept 2026
  • LowCVE-2022-41954Temporary File Information Disclosure vulnerability in MPXJ · 28 Nov 2022
  • CriticalCVE-2020-25020Improper Restriction of XML External Entity Reference in MPXJ · 7 May 2021
  • MediumCVE-2020-35460MPXJ path Traversal vulnerability · 18 Dec 2020
net.sf.mpxj:mpxj security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.