Futurio Extra <= 1.8.2 - Cross-Site Request Forgery via 'futurio_extra_reset_mod'
Strategic Overview
- Status
- Patched in 1.8.3
- Affected Plugin
- Futurio Extra
- Affected Version
<= 1.8.2- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2023-40201
At a glance
CVE-2023-40201 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Futurio Extra WordPress plugin, affecting versions <= 1.8.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.8.3; sites on affected versions should update now. Disclosed August 2023, reported by István Márton.
Vulnerability Overview
The Futurio Extra plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.8.2. This is due to missing or incorrect nonce validation on the 'futurio_extra_reset_mod' function. This makes it possible for unauthenticated attackers to reset theme modifications via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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.
CWE-352: Cross-Site Request Forgery (CSRF)
Futurio Extra <= 1.8.2 carries this weakness at futurio_extra_reset_mod, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Futurio Extra the fix is 1.8.3: builds <= 1.8.2 are affected, anything from 1.8.3 onward is not.
Remediation
Update to version 1.8.3, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Futurio Extra: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Futurio Extra 1.8.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
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-2024-10695: Futurio Extra <= 2.0.13 Post Disclosure
CVE-2024-10695 - 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