CVE-2024-7262
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 a deceptive spreadsheet document
do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.
Also consider: canonical path validation
Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2024-7262 being exploited?
Yes. CVE-2024-7262 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-7262?
CVE-2024-7262 is rated High with a CVSS score of 7.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-7262?
Yes. A fix has been recorded for CVE-2024-7262. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-7262 affect?
CVE-2024-7262 affects kingsoft:wps_office. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected>= 12.2.0.13110 and < 12.2.0.16412
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 31 Aug 2024 (SSVC 2.0.3).
timeline
- 15 Aug 2024Published
- 31 Aug 2024CISA SSVC assessment: exploitation active · 16 days later
- 3 Sept 2024Added to CISA KEV (exploited in the wild) · 3 days later
- 24 Sept 2024CISA remediation due date (US federal agencies) · 21 days later
- 21 Oct 2025CVE record last updated · 393 days (about 1 year) later
- 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.