Simple Restrict <= 1.2.6 - Missing Authorization to Sensitive Information Exposure
Strategic Overview
- Status
- Patched in 1.2.7
- Affected Plugin
- Simple Restrict
- Affected Version
<= 1.2.6- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2024-1083
At a glance
CVE-2024-1083 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Simple Restrict WordPress plugin, affecting versions <= 1.2.6. 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 1.2.7; sites on affected versions should update now. Disclosed March 2024, reported by Francesco Carlucci.
Vulnerability Overview
The Simple Restrict plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.2.6 via the REST API. This makes it possible for authenticated attackers to bypass the plugin's restrictions to extract post titles and content
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 Simple Restrict <= 1.2.6 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 Simple Restrict the fix is 1.2.7: builds <= 1.2.6 are affected, anything from 1.2.7 onward is not.
Remediation
Update to version 1.2.7, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: Simple Restrict 1.2.7 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C