CVE-2024-6472 | Ability to trust not validated macro signatures removed in high security mode

Certificate Validation user interface in LibreOffice allows potential vulnerability. Signed macros are scripts that have been digitally signed by the developer using a cryptographic signature. When a document with a signed macro is opened a warning is displayed by LibreOffice before the macro is executed. Previously if verification failed the user could fail to understand the failure and choose to enable the macros anyway. This issue affects LibreOffice: from 24.2 before 24.2.5.

Published: 2024-08-05 Last update: 2025-12-10 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2024-6472 is rated Low Risk (38.4/100): CVSS High severity, with low exploitation likelihood (EPSS 0.07%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-6472

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-21 0.04% 0.07% +0.03%
2 2025-11-18 0.06% 0.04% -0.02%
3 2025-09-13 0.06%

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-6472

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.8 5.9 [email protected]

Weakness enumeration for CVE-2024-6472

OS Trackers for CVE-2024-6472

vendor priority summary link
debian not yet assigned CVE-2024-6472 not yet assigned priority: Debian including 1 source packages (libreoffice), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2024-6472
redhat medium https://access.redhat.com/security/cve/CVE-2024-6472
suse high CVE-2024-6472 severity important: SUSE including 146 source package names (libreoffice, libreoffice-base, …), 817 product×package rows across 8 product lines (SUSE Linux Enterprise Module for Package Hub 15 SP5, SUSE Linux Enterprise Module for Package Hub 15 SP6, … (8 product lines)): Known Not Affected 817. https://www.suse.com/security/cve/CVE-2024-6472/
ubuntu medium CVE-2024-6472 medium priority: Ubuntu including 1 source packages (libreoffice), 4 status rows across 4 suites (focal, jammy, noble, upstream): released 4. https://ubuntu.com/security/CVE-2024-6472

Affected software / configurations for CVE-2024-6472

Vendor Product Version Raw CPE
libreoffice libreoffice >= 24.2.0.0, < 24.2.5.1 cpe:2.3:a:libreoffice:libreoffice:*:*:*:*:*:*:*:*

References for CVE-2024-6472

cvelogic Threat Intelligence