dbcve.org
Wps OfficeApplication · Kingsoft

CVE-2022-26081

HIGH · 7.8 CVSS v3.1 Published 2022-03-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
The installer of WPS Office Version 10.8.0.5745 insecurely load shcore.dll, allowing an attacker to execute arbitrary code with the privilege of the user invoking the installer.

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 confidence

The WPS Office installer version 10.8.0.5745 performs insecure DLL loading of shcore.dll, allowing an attacker to place a malicious DLL in the search path and achieve arbitrary code execution with the privileges of the user running the installer.

MitigationAvoid running the WPS Office installer in untrusted or shared environments until an official patched version is available from the vendor; verify and update to the latest secure version.

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
Wps OfficeApplication
Affected:= 10.8.0.5745

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate WPS Office installer on the system
    Search common download directories (e.g., Downloads folder) or installation locations for files named similar to 'wps_office_setup.exe' or 'Kingsoft Office installer'. Check Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for WPS Office entries.
    Affected if The installer file version is 10.8.0.5745
  2. Verify the exact installer version
    Right-click the installer executable, select Properties, then view the Details tab to find the File Version or Product Version field.
    Affected if The displayed version equals exactly 10.8.0.5745
  3. Check the installed WPS Office version
    Open Windows Control Panel > Programs and Features, locate Kingsoft WPS Office in the list, and note the version column. Alternatively, launch WPS Office application and check Help > About.
    Affected if The installed application version corresponds to installer version 10.8.0.5745 (the vulnerable installer was used)
  4. Inspect DLL search path vulnerability
    Run the installer with Process Monitor (from Sysinternals) filtering by the installer process name and looking for attempts to load shcore.dll from directories writable by the user (such as the installer directory itself or %TEMP%).
    Affected if The installer attempts to load shcore.dll from a user-writable directory rather than system directories only

You are affected if you have run or possess the WPS Office installer version 10.8.0.5745, as this specific version performs insecure DLL loading of shcore.dll.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Avoid running the WPS Office installer in untrusted or shared environments until an official patched version is available from the vendor; verify and update to the latest secure version.

Recommended fix Moderate confidence

Latest available WPS Office version (vendor should have patched DLL hijack in subsequent releases)

  1. 1. Uninstall the affected WPS Office version 10.8.0.5745 using the standard uninstallation process
  2. 2. Download the latest version of WPS Office from the official vendor website (support.kingsoft.jp or wps.com)
  3. 3. Verify the downloaded installer file integrity using checksums if provided by the vendor
  4. 4. Run the installer from a trusted directory (such as the user's Downloads folder or Desktop)
  5. 5. Complete the installation following the vendor's installation wizard

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wps Office Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26081 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-26081 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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