Cookies and Content Security Policy <= 2.15 - Sensitive Information Exposure
Strategic Overview
- Status
- Patched in 2.16
- Affected Plugin
- Cookies and Content Security Policy
- Affected Version
<= 2.15- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2023-40662
At a glance
CVE-2023-40662 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Cookies and Content Security Policy WordPress plugin, affecting versions <= 2.15. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.16; sites on affected versions should update now. Disclosed August 2023, reported by Kévin Mosbahi (Mika).
Vulnerability Overview
The Cookies and Content Security Policy plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 2.15 via the cacsp_texts function. This can allow unauthenticated attackers to extract sensitive data including the administrator email address.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in Cookies and Content Security Policy <= 2.15 takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Cookies and Content Security Policy the fix is 2.16: builds <= 2.15 are affected, anything from 2.16 onward is not.
Remediation
Update to version 2.16, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: Cookies and Content Security Policy 2.16 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C