dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-1785

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Contests by Rewards Fuel WordPress plugin is vulnerable to Cross-Site Request Forgery (CSRF) in versions up to 2.0.62 due to missing nonce validation in the ajax_handler() function. This allows unauthenticated attackers to forge requests that can update plugin settings and inject malicious JavaScript (stored XSS), provided they can socially engineer a user with edit_posts capability into clicking a malicious link.

MitigationUpdate the plugin to version 2.0.63 or later, which includes proper nonce validation for the ajax_handler() function. Until then, ensure administrators avoid clicking untrusted links.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm plugin installation
    Check if the Contests by Rewards Fuel plugin is installed in the WordPress plugins directory (wp-content/plugins/). Look for a folder named 'contests-by-rewards-fuel' or similar.
    Affected if The plugin folder exists in the WordPress installation.
  2. Identify installed version
    Open the main plugin file (usually contets-by-rewards-fuel.php or similar in the plugin folder) and locate the version in the plugin header comment. Alternatively, check the WordPress admin Plugins page for the installed version.
    Affected if The installed version is 2.0.62 or lower.
  3. Verify ajax_handler function exists
    Examine the plugin source code for the ajax_handler() function. This is typically found in the main plugin file or an included PHP file handling AJAX requests.
    Affected if The ajax_handler() function exists in the plugin code.
  4. Check nonce validation presence
    Review the ajax_handler() function code for nonce validation calls. Look for statements like 'wp_verify_nonce', 'check_admin_referer', or 'check_ajax_referer' within the function.
    Affected if No nonce verification is found within the ajax_handler() function.
  5. Assess user exposure
    Identify users with edit_posts capability on the site. The vulnerability requires a victim with this capability to click a maliciously crafted link.
    Affected if There are users with edit_posts capability who could be targeted for social engineering attacks.

A user is affected if the Contests by Rewards Fuel plugin version is 2.0.62 or lower and the ajax_handler() function lacks nonce validation, combined with the presence of users having edit_posts capability who could be socially engineered.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 2.0.63 or later, which includes proper nonce validation for the ajax_handler() function. Until then, ensure administrators avoid clicking untrusted links.

Recommended fix Moderate confidence

Contests by Rewards Fuel version 2.0.63 or latest available version

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Contests by Rewards Fuel' plugin
  4. Check if an update is available and update to the latest version
  5. Alternatively, download the latest version from wordpress.org/plugins/contests-by-rewards-fuel/ and upload via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin version is 2.0.63 or higher in the plugins list

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1785 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1785 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data