Cyber Resilience

CVE-2018-16858

Path Traversal in Libreoffice ≤ 6.0.7

Public PoCHigh EPSSPath Traversal
Published
25 March 2019
Modified
21 November 2024
Patch / advisory
CVSS Score v3 7.8
Click a component to see what it means
Raw vectorCVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.67 99.2th percentile
Risk Priority 83 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2018-16858 is a high-severity Product UI does not Warn User of Unsafe Actions (CWE-356) vulnerability in Libreoffice Libreoffice. Its CVSS base score is 7.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 0.8% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

It was found that libreoffice before versions 6.0.7 and 6.1.3 was vulnerable to a directory traversal attack which could be used to execute arbitrary macros bundled with a document. An attacker could craft a document, which when opened by LibreOffice,…

more

would execute a Python method from a script in any arbitrary file system location, specified relative to the LibreOffice install location.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1204 User Execution Execution
An adversary may rely upon specific actions by a user in order to gain execution.
T1204.001 Malicious Link Execution
An adversary may rely upon a user clicking a malicious link in order to gain execution.
T1204.002 Malicious File Execution
An adversary may rely upon a user opening a malicious file in order to gain execution.
T1204.004 Malicious Copy and Paste Execution
An adversary may rely upon a user copying and pasting code in order to gain execution.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-12425Same product: Libreoffice Libreoffice
CVE-2023-1183Same product: Libreoffice Libreoffice
CVE-2025-59304Shared CWE-22
CVE-2025-7694Shared CWE-22
CVE-2026-12198Shared CWE-22
CVE-2024-25154Shared CWE-22
CVE-2026-29050Shared CWE-22
CVE-2024-49082Shared CWE-22
CVE-2024-12362Shared CWE-22
CVE-2025-69377Shared CWE-22

Affected Assets

libreoffice
libreoffice
≤ 6.0.7 · 6.1.0 — 6.1.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 1 hardening rule · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)
  • V5.3.2

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-356

Mandates explicit user-visible indication, directly countering absence of warnings for device activation.

addresses: CWE-22

Validates pathnames and filenames to prevent traversal outside intended directories.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices include UI design requirements that warn users before unsafe actions.

PR.PS-02 partial match
prevents

Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.

PR.AA-05 none match
prevents

PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can verify presence of warnings for unsafe user actions.

prevents

Security awareness training can teach users to heed or demand warnings for unsafe actions.

prevents

Secure development life cycle requires UI design to warn users before unsafe actions.

prevents

Application security requirements include user warnings for dangerous operations.

prevents

Secure architecture principles can mandate confirmation prompts for risky actions.

prevents

Secure coding practices can embed user warnings before unsafe operations.

References