CVE-2024-7262
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 · uneditedImproper 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
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 confidenceImproper path validation in promecefpluginhost.exe allows DLL hijacking - the WPS Office component loads arbitrary Windows libraries from attacker-controlled locations when a user opens a malicious spreadsheet document, enabling code execution.
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>= 12.2.0.13110, < 12.2.0.16412CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed WPS Office versionOpen WPS Office application, click the account/profile icon or menu, and locate the version number in the About section or settings. Alternatively, check the program's properties in the installation directory.Affected if The installed version falls within >= 12.2.0.13110 and < 12.2.0.16412
-
Locate the promecefpluginhost.exe componentSearch for the file promecefpluginhost.exe in the WPS Office installation directory (commonly under C:\Program Files\Kingsoft\wps\ or similar paths).Affected if The file promecefpluginhost.exe exists in the WPS Office installation folder
-
Verify spreadsheet (ET) component is presentConfirm that the WPS Office spreadsheet application (typically named et.exe) is installed and functional.Affected if The spreadsheet/ET component is installed and operational
-
Check for untrusted document handling capabilityDetermine whether the system is configured to open spreadsheet documents (.xlsx, .xls, .et) through WPS Office.Affected if The system can open spreadsheet documents using WPS Office
You are affected if WPS Office version is 12.2.0.13110 through 12.2.0.16411 and you use the spreadsheet functionality to open documents.
Generated from the published advisory. Verify against your own configuration.
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 · scoped12.2.0.16412
Update Kingsoft WPS Office to version 12.2.0.16412 or later to patch the path validation vulnerability; avoid opening untrusted documents from unknown sources.
WPS Office 12.2.0.16412 or later
- Open WPS Office and navigate to Help > About WPS Office to check the current installed version
- Visit the official WPS Office download page at www.wps.com to obtain the latest version
- Download and install WPS Office version 12.2.0.16412 or later
- Restart WPS Office after the installation completes
- Verify the installed version is 12.2.0.16412 or higher via Help > About WPS Office
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7262 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-7262 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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