CVE-2025-0514
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 · uneditedImproper Input Validation vulnerability in The Document Foundation LibreOffice allows Windows Executable hyperlink targets to be executed unconditionally on activation.This issue affects LibreOffice: from 24.8 before < 24.8.5.
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 confidenceLibreOffice contains an improper input validation vulnerability in its hyperlink handling that allows Windows executable hyperlink targets to execute unconditionally when activated, leading to potential arbitrary code execution.
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>= 24.8.0.0, < 24.8.5.1CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check LibreOffice version on WindowsOpen LibreOffice Writer, go to Help > About LibreOffice (or LibreOffice > About LibreOffice on macOS). Note the exact version number displayed.Affected if The version is >= 24.8.0.0 and < 24.8.5.1, indicating the vulnerable release.
-
Check LibreOffice version via command lineRun the command 'soffice --version' in Command Prompt or PowerShell on Windows, or via terminal on Linux/macOS. Capture the output showing the full version string.Affected if The reported version falls within the affected range of 24.8.0.0 through 24.8.5.0.
-
Identify documents with hyperlinksOpen any document (ODT, DOCX, etc.) in LibreOffice. Press Ctrl+F to open the Find toolbar, then search for 'http:' or 'https:' patterns, or manually scroll through the document looking for blue underlined text indicating hyperlinks.Affected if Documents containing any hyperlinks are present, as the vulnerability triggers when these hyperlinks are activated.
-
Confirm Windows platformVerify the operating system is Windows by checking system information (winver command or System Properties).Affected if LibreOffice is running on Windows, since the flaw specifically allows Windows executable hyperlink targets to execute unconditionally.
A user is affected if LibreOffice version is between 24.8.0.0 and 24.8.5.0 (inclusive) on Windows, and they open documents containing hyperlinks that point to Windows executables.
Generated from the published advisory. Verify against your own configuration.
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 · scoped24.8.5.1
Upgrade to LibreOffice 24.8.5 or later to patch the vulnerability; avoid opening untrusted documents with hyperlinks until the update is applied.
24.8.5.1 or later
- Upgrade LibreOffice to version 24.8.5.1 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0514 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-0514 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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