Contests by Rewards Fuel <= 2.0.62 - Cross-Site Request Forgery to Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 2.0.63
- Affected Plugin
- Contests by Rewards Fuel
- Affected Version
<= 2.0.62- CVSS
- 5.4Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-1785
At a glance
CVE-2024-1785 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Contests by Rewards Fuel WordPress plugin, affecting versions <= 2.0.62. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.0.63; sites on affected versions should update now. Disclosed March 2024, reported by Sean Bales.
Vulnerability Overview
The Contests by Rewards Fuel plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.0.62. This is due to missing or incorrect nonce validation on the ajax_handler() function. This makes it possible for unauthenticated attackers to update the plugin's settings and inject malicious JavaScript via a forged request granted they can trick a site's user with the edit_posts capability 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)
Contests by Rewards Fuel <= 2.0.62 carries this weakness at ajax_handler(), 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 Contests by Rewards Fuel the fix is 2.0.63: builds <= 2.0.62 are affected, anything from 2.0.63 onward is not.
Remediation
Update to version 2.0.63, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Contests by Rewards Fuel: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Contests by Rewards Fuel 2.0.63 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Contests by Rewards Fuel
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C