CVE-2024-7263
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.17115 (exclusive) on Windows allows an attacker to load an arbitrary Windows library. The patch released in version 12.1.0.17119 to mitigate CVE-2024-7262 was not restrictive enough. Another parameter was not properly sanitized which leads to the execution of an arbitrary Windows library.
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 loading of arbitrary Windows libraries (DLL hijacking) due to incomplete sanitization of an additional parameter not addressed in the CVE-2024-7262 fix. Attackers can execute malicious code by placing a crafted DLL in a location where the application loads libraries.
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.17153CVSS 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 WPS Office installationCheck if Kingsoft WPS Office is installed on the system by looking for the program in Add/Remove Programs or searching for WPS Office installation directories (typically C:\Program Files\Kingsoft\WPS Office or C:\Users\%username%\AppData\Local\Kingsoft\WPS Office)Affected if WPS Office is installed and the version falls within the affected range
-
Determine installed WPS Office versionLocate the WPS Office installation and check the version. Common locations include the program's main executable or version info in the installation folder. The version typically appears in the format 12.2.x.x where x represents build numbersAffected if The installed version is >= 12.2.0.13110 and < 12.2.0.17153
-
Verify vulnerable component existsCheck if promecefpluginhost.exe exists in the WPS Office installation directory. This file is the specific component with the improper path validation vulnerabilityAffected if promecefpluginhost.exe is present in the WPS Office installation folder
-
Check DLL search path locationsExamine directories where WPS Office loads libraries, particularly the application directory and any subdirectories where promecefpluginhost.exe may load DLLs from. Look for any unexpected or suspicious DLL files that were not part of a normal installationAffected if Unexpected DLL files exist in directories from which promecefpluginhost.exe loads libraries, indicating potential hijacking attempt
A system is affected if Kingsoft WPS Office version 12.2.0.13110 through 12.2.0.17152 is installed and contains the vulnerable promecefpluginhost.exe component.
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.17153
Upgrade WPS Office to version 12.2.0.17115 or later which contains the complete fix for improper path validation in promecefpluginhost.exe.
12.2.0.17153 or later
- Download WPS Office version 12.2.0.17153 or later from the official website (www.wps.com)
- Close any running WPS Office applications
- Run the installer to upgrade to the fixed version
- After installation, verify the version by checking Help > About WPS Office to confirm you are on 12.2.0.17153 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7263 — 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-7263 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