Futurio Extra <= 2.0.13 - Authenticated (Contributor+) Post Disclosure
Strategic Overview
- Status
- Patched in 2.0.14
- Affected Plugin
- Futurio Extra
- Affected Version
<= 2.0.13- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2024-10695
At a glance
CVE-2024-10695 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Futurio Extra WordPress plugin, affecting versions <= 2.0.13. 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 2.0.14; sites on affected versions should update now. Disclosed November 2024, reported by Francesco Carlucci.
Vulnerability Overview
The Futurio Extra plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 2.0.13 via the 'elementor-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 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
Futurio Extra <= 2.0.13 carries this weakness at elementor-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 Futurio Extra the fix is 2.0.14: builds <= 2.0.13 are affected, anything from 2.0.14 onward is not.
Remediation
Update to version 2.0.14, 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: Futurio Extra 2.0.14 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Futurio Extra
- 7.2CVE-2021-25109: Futurio Extra <= 1.6.2 SQL Injection
CVE-2021-25109 - 6.4CVE-2024-53802: Futurio Extra <= 2.0.14 Stored Cross-Site Scripting
CVE-2024-53802 - 6.4CVE-2024-50446: Futurio Extra <= 2.0.11 Stored Cross-Site Scripting
CVE-2024-50446 - 6.4CVE-2024-5646: Futurio Extra <= 2.0.5 Stored Cross-Site Scripting
CVE-2024-5646 - 4.3CVE-2023-40201: Futurio Extra <= 1.9.0 Cross-Site Request Forgery
CVE-2023-40201 - 4.3CVE-2023-40201: Futurio Extra <= 1.8.2 Cross-Site Request Forgery
CVE-2023-40201 - 4.3CVE-2021-25110: Futurio Extra <= 1.6.2 Info Disclosure
CVE-2021-25110
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C