CVE-2024-7262
Path Traversal in Kingsoft Wps Office 12.2.0.13110 – 12.2.0.16412
Raw vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:X/V:X/RE:L/U:XSummary
CVE-2024-7262 is a critical-severity Path Traversal (CWE-22) vulnerability in Kingsoft Wps Office. Its CVSS base score is 9.3 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 24% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-7262 is an improper path validation flaw (CWE-22) in promecefpluginhost.exe within Kingsoft WPS Office on Windows. It affects builds 12.2.0.13110 through 12.2.0.16412 (exclusive) and permits an attacker to load an arbitrary Windows library because the executable fails to correctly sanitize or restrict the search path for DLLs.
An unauthenticated local attacker can deliver a single-click exploit via a deceptive spreadsheet document. When the victim opens the file, the vulnerable host process loads attacker-controlled code, resulting in arbitrary code execution with full confidentiality, integrity Availability, and scope impacts as reflected in the CVSS 9.3 score.
WPS released an updated build on 22 April 2024 that corrects the path-handling logic. CISA added the CVE to its Known Exploited Vulnerabilities catalog, confirming that the flaw has been observed in active campaigns and directing organizations to apply the vendor patch.
The EPSS score rose from a low baseline to a peak of 0.1747 before settling at 0.1029, indicating measurable post-disclosure exploitation interest that aligns with its inclusion in the CISA catalog.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-48209
Vulnerability Data
Improper path validation in promecefpluginhost.exe in Kingsoft WPS Office version ranging from 12.2.0.13110 to 12.2.0.16412 (exclusive) on Windows allows an attacker to load an arbitrary Windows library. The vulnerability was found weaponized as a single-click exploit in the form of…
more
a deceptive spreadsheet document
- CWE(s)
- KEV Date Added
- 03 September 2024
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces the intended directory access authorizations that path traversal would otherwise bypass.
Input validation directly neutralizes special path elements before pathname construction occurs.
Least privilege reduces the impact of any unauthorized file access obtained via traversal.
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.
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 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.
Security testing in development catches path traversal via static/dynamic analysis.
Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.
Application security requirements include rules for safe file handling and canonicalization.
Secure architecture principles require least-privilege file access and directory isolation.
Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.
Information access restriction limits which files an application may read or write.