CVE-2022-26511
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 · uneditedWPS Presentation 11.8.0.5745 insecurely load d3dx9_41.dll when opening .pps files('current directory type' DLL loading).
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 confidenceWPS Presentation 11.8.0.5745 attempts to load the d3dx9_41.dll library from the current working directory when opening .pps files, allowing an attacker to place a malicious DLL in the same directory as a specially crafted .pps file to achieve arbitrary code execution with the privileges of the user opening the file.
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= 11.8.0.5745CVSS 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 Presentation installation pathCheck the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wps.exe or HKCU\SOFTWARE\Kingsoft\Office\WPP for the installation directory, or look in common paths like C:\Program Files\Kingsoft\WPS Office\wpp.exeAffected if WPS Presentation is installed and the executable exists at the expected location
-
Determine installed WPS Presentation versionRight-click wps.exe or wpp.exe, select Properties, and check the File Version field on the Details tab, or run: wmic datafile where "name='C:\\Program Files\\Kingsoft\\WPS Office\\wpp.exe'" get VersionAffected if The version shown is exactly 11.8.0.5745
-
Verify .pps file association with WPS PresentationCheck registry HKCR\.pps\OpenWithProgids or look for .pps file type association to WPS Presentation, or right-click any .pps file and check 'Opens with' to confirm it uses WPS PresentationAffected if WPS Presentation is set as the default handler for .pps files
-
Confirm vulnerable DLL search behaviorWhen WPS Presentation opens a .pps file from a directory containing a malicious d3dx9_41.dll, the application will attempt to load that DLL from the current working directory rather than using a secure pathAffected if WPS Presentation version 11.8.0.5745 is used to open .pps files from directories where d3dx9_41.dll could be placed
You are affected if WPS Presentation version 11.8.0.5745 is installed and configured to open .pps files, as the application will load d3dx9_41.dll from the current working directory allowing DLL hijacking.
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 dataUsers should avoid opening .pps files from untrusted or shared/network directories. The vendor should implement secure DLL loading by using absolute paths, safe library loading functions (e.g., SetDllDirectory with empty string to clear unsafe paths), and embedding manifest files to specify safe DLL search order.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26511 — 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-2022-26511 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