Attesa Extra <= 1.4.2 - Authenticated (Contributor+) Post Disclosure
Strategic Overview
- Status
- Patched in 1.4.3
- Affected Plugin
- Attesa Extra
- Affected Version
<= 1.4.2- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2024-10688
At a glance
CVE-2024-10688 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Attesa Extra WordPress plugin, affecting versions <= 1.4.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 1.4.3; sites on affected versions should update now. Disclosed November 2024, reported by Francesco Carlucci.
Vulnerability Overview
The Attesa Extra plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 1.4.2 via the 'attesa-template' shortcode due to insufficient restrictions on which posts can be included. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract data from password protected, private, or draft posts that they should not have access to.
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 interaction from a victim user.
CWE-639: Authorization Bypass Through User-Controlled Key
Attesa Extra <= 1.4.2 carries this weakness at attesa-template, and reaching it takes an account at Contributor level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Attesa Extra the fix is 1.4.3: builds <= 1.4.2 are affected, anything from 1.4.3 onward is not.
Remediation
Update to version 1.4.3, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Attesa Extra 1.4.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C