dbcve.org
PoiApplication · Apache

CVE-2025-31672

MEDIUM · 5.3 CVSS v3.1 Published 2025-04-09
Fix available
A fix is available. Upgrade to 5.4.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Input Validation vulnerability in Apache POI. The issue affects the parsing of OOXML format files like xlsx, docx and pptx. These file formats are basically zip files and it is possible for malicious users to add zip entries with duplicate names (including the path) in the zip. In this case, products reading the affected file could read different data because 1 of the zip entries with the duplicate name is selected over another but different products may choose a different zip entry. This issue affects Apache POI poi-ooxml before 5.4.0. poi-ooxml 5.4.0 has a check that throws an exception if zip entries with duplicate file names are found in the input file. Users are recommended to upgrade to version poi-ooxml 5.4.0, which fixes the issue. Please read https://poi.apache.org/security.html for recommendations about how to use the POI libraries securely.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache POI's OOXML parser (for xlsx, docx, pptx) does not properly validate zip entry names when parsing these file formats. Malicious files can contain duplicate zip entries with identical names, causing different products to read different data depending on which entry each product selects.

MitigationUpgrade poi-ooxml library to version 5.4.0 or later, which throws an exception when duplicate zip entries are detected.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PoiApplication
Affected:< 5.4.0
Active Iq Unified ManagerApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache POI library version
    Check your project's dependency management (Maven pom.xml, Gradle build.gradle, or JAR file manifest) for the poi-ooxml library version
    Affected if The poi-ooxml version is below 5.4.0 or cannot be determined
  2. Identify NetApp Active IQ Unified Manager installation
    Check if NetApp Active IQ Unified Manager software is installed on the system
    Affected if NetApp Active IQ Unified Manager is present (all versions are affected)
  3. Determine if OOXML parsing is in use
    Identify whether your application or system processes Office Open XML files (xlsx, docx, pptx) using Apache POI
    Affected if OOXML files are being parsed and the Apache POI version is below 5.4.0 or the NetApp product is in use
  4. Check for duplicate zip entry handling
    Inspect whether your environment processes OOXML files from untrusted sources without additional validation
    Affected if Untrusted or external OOXML files are processed and the library version is vulnerable

You are affected if Apache POI with poi-ooxml library version below 5.4.0 is in use and processes OOXML files, or if NetApp Active IQ Unified Manager is installed regardless of version.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.4.0 or later
Fixed in 5.4.0
Interim mitigation

Upgrade poi-ooxml library to version 5.4.0 or later, which throws an exception when duplicate zip entries are detected.

Recommended fix High confidence

poi-ooxml 5.4.0

  1. 1. Identify all applications or systems that use Apache POI poi-ooxml library with version less than 5.4.0
  2. 2. Obtain Apache POI poi-ooxml version 5.4.0 or later from the official Apache POI distribution (https://poi.apache.org/download.html) or Maven repository
  3. 3. Replace the vulnerable poi-ooxml JAR file(s) in your project dependencies with version 5.4.0 or later
  4. 4. If using Maven or Gradle, update the dependency version to poi-ooxml:5.4.0 or higher
  5. 5. Rebuild and redeploy the application with the updated library
  6. 6. Test the application with legitimate OOXML files (xlsx, docx, pptx) to ensure functionality is maintained
  7. 7. For Active Iq Unified Manager users: contact NetApp support or check security.netapp.com for product-specific patches since this product affects all versions
Caveat Version 5.4.0 throws an exception when encountering OOXML files with duplicate zip entries - this is intentional security behavior but may cause failures with malformed files that were previously processed without error

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Poi Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-31672 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-31672 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data