CVE-2024-11957
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 verification of the digital signature in ksojscore.dll in Kingsoft WPS Office in versions equal or less than 12.1.0.18276 on Windows allows an attacker to load an arbitrary Windows library. The patch released in version 12.2.0.16909 to mitigate CVE-2024-7262 was not restrictive enough.
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 digital signature verification in ksojscore.dll allows attackers to load arbitrary Windows libraries (DLL hijacking). This stems from an incomplete fix for CVE-2024-7262, where the original patch was not restrictive enough to prevent malicious library loading.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/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:X/R:X/V:X/RE:X/U:X
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.
-
Locate the ksojscore.dll fileSearch for ksojscore.dll in the WPS Office installation directory (commonly C:\Program Files\WPS Office\ or C:\Program Files (x86)\WPS Office\) and note its full pathAffected if The DLL exists in the WPS Office installation directory
-
Check the file version of ksojscore.dllRight-click the DLL file, select Properties, then go to the Details tab to view the File Version valueAffected if The file version is earlier than 12.2.0.16909 (compare your version against this baseline)
-
Check the installed WPS Office versionOpen Windows Settings > Apps > Installed apps, find WPS Office, and view the version number, or use the command: wmic product where "name like 'WPS Office'%" get versionAffected if The WPS Office version is earlier than 12.2.0.16909
-
Inspect DLL search order loadingUse Sysinternal's Process Monitor or Dependency Walker to observe which directory ksojscore.dll is loaded from during WPS Office execution, checking for any path that allows user writable accessAffected if The DLL is being loaded from a directory with weak access controls or the current working directory
-
Verify digital signature statusRight-click ksojscore.dll, select Properties, then go to the Digital Signatures tab to check if a valid signature is present and the certificate is trustedAffected if The DLL has no valid digital signature or shows signature verification errors
You are affected if WPS Office or ksojscore.dll version is earlier than 12.2.0.16909 and the DLL can be loaded from a user-controlled location or lacks valid signature verification.
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.
From vendor dataUpgrade WPS Office to version 12.2.0.16909 or later to remediate this vulnerability. Verify that digital signature enforcement is functioning correctly after the upgrade.
- 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-11957 — 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-11957 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