dbcve.org
OpenofficeApplication · Apache

CVE-2025-64407

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-12
Fix available
A fix is available. Upgrade to 4.1.16 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
Apache OpenOffice documents can contain links. A missing Authorization vulnerability in Apache OpenOffice allowed an attacker to craft a document that would cause external links to be loaded without prompt. Such links could also be used to transmit system information, such as environment variables or configuration settings. In the affected versions of Apache OpenOffice, documents that used a certain URI scheme linking to external files would load the contents of such files without prompting the user for permission to do so. Such URI scheme allows to include system configuration data, that is not supposed to be transmitted externally. This issue affects Apache OpenOffice: through 4.1.15. Users are recommended to upgrade to version 4.1.16, which fixes the issue. The LibreOffice suite reported this issue as CVE-2024-12426.

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 OpenOffice contains a missing authorization vulnerability where documents with certain URI schemes can load external file contents without user prompting. Attackers can craft malicious documents that exfiltrate system configuration data, environment variables, and settings by triggering automatic loading of external content.

MitigationUpgrade Apache OpenOffice to version 4.1.16 or later to resolve the missing authorization check for URI scheme-based external file loading.

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
OpenofficeApplication
Affected:< 4.1.16

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 installed Apache OpenOffice version
    Open Apache OpenOffice, then go to Help > About to view the exact version number. Alternatively, check Add/Remove Programs on Windows or use the package manager on Linux systems.
    Affected if The displayed version number is less than 4.1.16 (for example, 4.1.15, 4.1.14, or earlier)
  2. Check OpenOffice program directory version file
    Navigate to the OpenOffice installation directory (commonly C:\Program Files\Apache Office on Windows or /opt/openoffice on Linux) and locate any version.txt or similar version information file.
    Affected if The version file shows a version lower than 4.1.16
  3. Verify version via command line
    On Windows, run the command 'reg query "HKLM\SOFTWARE\OpenOffice" /v Version' or on Linux check the output of 'rpm -q openoffice' or 'dpkg -l openoffice'.
    Affected if The reported version is below 4.1.16

If Apache OpenOffice version is 4.1.16 or later, the environment is not affected by this vulnerability; any version below 4.1.16 is affected.

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 4.1.16 or later
Fixed in 4.1.16
Interim mitigation

Upgrade Apache OpenOffice to version 4.1.16 or later to resolve the missing authorization check for URI scheme-based external file loading.

Recommended fix High confidence

4.1.16

  1. Back up any important documents before upgrading
  2. Download Apache OpenOffice version 4.1.16 from the official Apache OpenOffice website (www.openoffice.org)
  3. Uninstall the current version of Apache OpenOffice
  4. Install Apache OpenOffice 4.1.16
  5. Verify the installation by checking the version number in the application

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

Fix this in Openoffice Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64407 — 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-64407 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