CVE-2024-13187
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 · uneditedA vulnerability was found in Kingsoft WPS Office 6.14.0 on macOS. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the component TCC Handler. The manipulation leads to code injection. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 · moderate confidenceA code injection vulnerability exists in the TCC (Transparency, Consent, and Control) Handler component of Kingsoft WPS Office 6.14.0 on macOS. The vulnerability allows a local attacker to inject malicious code through manipulation of the application's TCC permission handling mechanism. This is a local attack vector requiring no network access.
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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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.
-
Verify WPS Office installationLocate WPS Office application on the macOS system, typically found in /Applications or ~/Applications. Use 'ls -la' or Finder to confirm the application bundle exists.Affected if WPS Office is installed on the system
-
Check installed WPS Office versionRight-click the WPS Office app, select 'Get Info', or use command: 'defaults read /Applications/WPS\ Office.app/Contents/Info CFBundleShortVersionString' to retrieve the version number.Affected if The version number matches 6.14.0 or falls within an earlier vulnerable version range
-
Examine TCC permissions for WPS OfficeQuery the TCC database using: 'sudo tccutil -l' or inspect ~/Library/Application\ Support/com.apple.TCC/TCC.db for entries related to WPS Office. Alternatively, check System Settings > Privacy & Security to view granted permissions.Affected if WPS Office has any TCC permissions granted, particularly for accessibility, automation, or other sensitive categories
-
Review TCC permission modificationsCheck system logs for TCC-related changes: 'log show --predicate 'eventMessage contains "WPS"' --last 7d' or examine /var/log/system.log for entries involving WPS Office and TCC modifications.Affected if Any recent TCC permission grants or modifications to WPS Office permissions are present in system logs
A user is affected if WPS Office version 6.14.0 is installed AND the application has been granted TCC permissions, enabling the code injection vector through the TCC Handler 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.
From vendor dataSince the vendor did not respond to early disclosure, no official patch is available. Organizations should restrict WPS Office's system permissions, monitor for suspicious behavior, and consider migrating to an alternative office suite until a patch is released.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13187 — 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-13187 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