Is net.sf.mpxj-for-vb 4.7 vulnerable?

NuGet · 6 releases from 4.7.0 to 4.7.6 · latest net.sf.mpxj-for-vb is 13.12.0 · checked 20 Nov 2026

Yes: 1 known advisory

Yes. net.sf.mpxj-for-vb 4.7.6, the last 4.7 release, is affected by 1 known security advisory (1 low), including CVE-2022-41954. Upgrade to 10.14.1 or later to fix all of them.

Upgrade with:dotnet add package net.sf.mpxj-for-vb --version 10.14.1

Is your project on an affected net.sf.mpxj-for-vb?

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

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

Advisories affecting net.sf.mpxj-for-vb 4.7.6

  • LowCVE-2022-41954GHSA-jf2p-4gqj-849g28 Nov 2022

    Temporary File Information Disclosure vulnerability in MPXJ

    Affected
    <10.14.1
    Fixed in
    10.14.1

Every net.sf.mpxj-for-vb 4.7.x release

Affected: 4.7.0 to 4.7.6. Latest net.sf.mpxj-for-vb: 13.12.0.

VersionKnown advisories
net.sf.mpxj-for-vb 4.7.6CVE-2022-41954
net.sf.mpxj-for-vb 4.7.5CVE-2022-41954
net.sf.mpxj-for-vb 4.7.4CVE-2022-41954
net.sf.mpxj-for-vb 4.7.3CVE-2022-41954
net.sf.mpxj-for-vb 4.7.1CVE-2022-41954
net.sf.mpxj-for-vb 4.7.0CVE-2022-41954

Which of your client projects are still on net.sf.mpxj-for-vb 4.7?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact net.sf.mpxj-for-vb version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other net.sf.mpxj-for-vb versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the NuGet registry. Refreshed daily.