Content Control <= 2.1.0 - Missing Authorization to Sensitive Information Exposure
Strategic Overview
- Status
- Patched in 2.2.0
- Affected Plugin
- Content Control – The Ultimate Content Restriction Plugin! Restrict Content, Create Conditional Blocks & More
- Affected Version
<= 2.1.0- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2024-0615
At a glance
CVE-2024-0615 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Content Control WordPress plugin, affecting versions <= 2.1.0. 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.2.0; sites on affected versions should update now. Disclosed April 2024, reported by Francesco Carlucci.
Vulnerability Overview
The Content Control – The Ultimate Content Restriction Plugin! Restrict Content, Create Conditional Blocks & More plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.1.0 via the API. This makes it possible for unauthenticated attackers to extract post titles, IDs, slugs, statuses and other information including post content. This includes published content only.
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 Content Control <= 2.1.0 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 Content Control the fix is 2.2.0: builds <= 2.1.0 are affected, anything from 2.2.0 onward is not.
Remediation
Update to version 2.2.0, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: Content Control 2.2.0 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Content Control – The Ultimate Content Restriction Plugin! Restrict Content, Create Conditional Blocks & More
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C