dbcve.org
OpenofficeApplication · Apache

CVE-2025-64402

MEDIUM · 6.5 CVSS v3.1 Published 2025-11-12
Fix available
A fix is available. Upgrade to 4.1.16 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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. In the affected versions of Apache OpenOffice, documents that used "OLE objects" linked to external files would load the contents of those files without prompting the user for permission to do so. This issue affects Apache OpenOffice: through 4.1.15. Users are recommended to upgrade to version 4.1.16, which fixes the issue.

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 · moderate confidence

Apache OpenOffice fails to prompt users before loading external files referenced via OLE object links in documents. When a document contains OLE objects linked to external files, those files are automatically loaded without user consent, potentially allowing malicious documents to exfiltrate data or trigger unwanted network requests.

MitigationUpgrade Apache OpenOffice to version 4.1.16. Additionally, disable automatic loading of external content or use enterprise document filtering to block untrusted documents until the upgrade is applied.

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
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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. Check Apache OpenOffice installed version
    Open Apache OpenOffice, then go to Help > About Apache OpenOffice to view the version number. Alternatively, check the program's file properties or use system package management tools to query the installed version.
    Affected if The installed version is lower than 4.1.16 (for example, 4.1.15, 4.1.14, or earlier)
  2. Identify documents with OLE object links
    Examine document files (particularly .odt, .doc, .docx) for embedded OLE objects that reference external file paths or URLs. In OpenOffice Writer, view the document structure or check Insert > Object > OLE Object to identify embedded objects.
    Affected if Documents contain OLE objects linked to external files without embedded content
  3. Review automatic content loading settings
    Go to Tools > Options > Security in Apache OpenOffice and examine settings related to external content, OLE objects, or automatic file loading. Check if there are options enabled that allow automatic retrieval of linked content.
    Affected if Settings permit automatic loading of external content from OLE links without prompting

A user is affected if they have Apache OpenOffice version below 4.1.16 and open documents containing OLE objects with external links, as the external files will load automatically without user consent.

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. Additionally, disable automatic loading of external content or use enterprise document filtering to block untrusted documents until the upgrade is applied.

Recommended fix High confidence

4.1.16

  1. 1. Visit the official Apache OpenOffice download page at https://www.openoffice.org/download/
  2. 2. Download Apache OpenOffice version 4.1.16 for your operating system
  3. 3. Uninstall the current version of Apache OpenOffice (versions prior to 4.1.16)
  4. 4. Install Apache OpenOffice 4.1.16 using the downloaded installer

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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