dbcve.org
Debian LinuxOperating system · Debian

CVE-2025-1080

HIGH · 7.8 CVSS v3.1 Published 2025-03-04
Fix available
A fix is available. Upgrade to 24.8.5.1 / 25.2.1.1 or later.
See remediation →
81/100
Remediation priority · High
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
LibreOffice supports Office URI Schemes to enable browser integration of LibreOffice with MS SharePoint server. An additional scheme 'vnd.libreoffice.command' specific to LibreOffice was added. In the affected versions of LibreOffice a link in a browser using that scheme could be constructed with an embedded inner URL that when passed to LibreOffice could call internal macros with arbitrary arguments. This issue affects LibreOffice: from 24.8 before < 24.8.5, from 25.2 before < 25.2.1.

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

LibreOffice's 'vnd.libreoffice.command' URI scheme allows malicious URLs to embed an inner URL that, when processed by LibreOffice, can invoke internal macros with arbitrary arguments, leading to arbitrary code execution. This is a command injection vulnerability via browser-to-application URI scheme handling.

MitigationUpgrade to LibreOffice 24.8.5 or 25.2.1 or later to patch the URI scheme handling vulnerability. Consider disabling the vulnerable URI scheme as a temporary workaround if immediate upgrading is not feasible.

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
Debian LinuxOperating system
Affected:= 11.0
LibreofficeApplication
Affected:>= 24.8.0.0, < 24.8.5.1>= 25.2.0.0, < 25.2.1.1

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
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 checks

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

  1. Check if LibreOffice is installed
    Run 'dpkg -l | grep -i libreoffice' on Debian, or check for 'libreoffice' in Programs and Features on Windows, or 'rpm -qa | grep -i libreoffice' on RHEL-based systems
    Affected if LibreOffice is installed on the system
  2. Determine the installed LibreOffice version
    Run 'libreoffice --version' or 'soffice --version' from command line, or check the package version via dpkg/rpm
    Affected if The installed version is >= 24.8.0.0 and < 24.8.5.1, OR >= 25.2.0.0 and < 25.2.1.1
  3. Verify if the vnd.libreoffice.command URI scheme is registered
    On Linux, check /usr/share/applications/*.desktop files for 'vnd.libreoffice.command' in MimeType fields, or examine the registry or system URI handler configuration
    Affected if The URI scheme handler for vnd.libreoffice.command exists and is accessible to the current user
  4. Confirm browser-to-application URI handling is enabled
    Check if LibreOffice is configured as a handler for URL schemes in the desktop environment or browser settings, or inspect /etc/gnome/defaults.list and similar configuration files
    Affected if The system or browser is configured to open LibreOffice via URI schemes including vnd.libreoffice.command

You are affected if LibreOffice is installed with a version in the ranges 24.8.0.0-24.8.5.0 or 25.2.0.0-25.2.1.0 AND the vnd.libreoffice.command URI scheme handler is registered and accessible on your system.

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 24.8.5.1 / 25.2.1.1 or later
Fixed in 24.8.5.125.2.1.1
Interim mitigation

Upgrade to LibreOffice 24.8.5 or 25.2.1 or later to patch the URI scheme handling vulnerability. Consider disabling the vulnerable URI scheme as a temporary workaround if immediate upgrading is not feasible.

Recommended fix High confidence

LibreOffice 24.8.5.1 or later, or LibreOffice 25.2.1.1 or later

  1. Identify the currently installed LibreOffice version using Help > About LibreOffice or by running 'libreoffice --version'
  2. Determine which upgrade path applies: if using 24.8.x, upgrade to 24.8.5.1 or later; if using 25.2.x, upgrade to 25.2.1.1 or later
  3. For Debian systems, update package lists with 'sudo apt update' and upgrade LibreOffice with 'sudo apt upgrade libreoffice'
  4. Alternatively, download the fixed version directly from the official LibreOffice website (www.libreoffice.org)
  5. Verify the upgrade was successful by checking the version again
  6. Ensure any custom URI scheme configurations or macro settings are reviewed after upgrade

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

Fix this in Debian Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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