dbcve.org
BenevolentWordPress extension · Rarathemes

CVE-2024-37450

HIGH · 8.8 CVSS v3.1 Published 2025-01-02
Fix available
A fix is available. Upgrade to 1.3.5 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Cross-Site Request Forgery (CSRF) vulnerability in raratheme Benevolent benevolent allows Cross Site Request Forgery.This issue affects Benevolent: from n/a through <= 1.3.4.

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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Benevolent WordPress theme (versions <= 1.3.4) allows remote attackers to trick authenticated users into submitting unintended requests to the site, potentially modifying data or performing administrative actions without proper authorization.

MitigationImplement WordPress nonces (anti-CSRF tokens) on all state-changing operations (forms, AJAX endpoints, URL-based actions) and verify the nonce before processing any requests. Additionally, consider adding SameSite cookie attributes and origin validation.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
BenevolentWordPress extension
Affected:< 1.3.5

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
High
Integrity
High
Availability
High

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

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 Benevolent theme is installed
    In WordPress admin, go to Appearance > Themes and check if the Benevolent theme by Rarathemes is active or installed
    Affected if Benevolent theme is installed and active on the site
  2. Identify installed theme version
    Access the theme directory via FTP or file manager, open the file /wp-content/themes/benevolent/style.css, and locate the 'Version:' field in the theme header comment
    Affected if Version number found is less than 1.3.5 (e.g., 1.3.4, 1.3.3, etc.)
  3. Inspect theme forms for nonce fields
    Examine theme template files (typically in /wp-content/themes/benevolent/) that contain HTML forms. Look for wp_nonce_field() or wp_nonce_url() function calls inside form definitions. Common files to check include search forms, comment forms, and any custom forms in template files.
    Affected if Forms in the theme templates lack wp_nonce_field() or equivalent nonce implementations
  4. Check AJAX handlers for nonce verification
    Search theme PHP files for add_action('wp_ajax_') or add_action('wp_ajax_nopriv_') calls. For each AJAX handler found, verify that the handler includes a nonce check such as check_ajax_referer() or wp_verify_nonce() before processing the request.
    Affected if AJAX endpoints defined by the theme do not validate nonces before processing requests

Your environment is affected if the Benevolent theme version is below 1.3.5 AND the theme forms or AJAX handlers lack proper nonce validation.

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
Upgrade available Upgrade to 1.3.5 or later
Fixed in 1.3.5
Interim mitigation

Implement WordPress nonces (anti-CSRF tokens) on all state-changing operations (forms, AJAX endpoints, URL-based actions) and verify the nonce before processing any requests. Additionally, consider adding SameSite cookie attributes and origin validation.

Recommended fix Moderate confidence

1.3.5

  1. Check current Benevolent theme version in WordPress admin under Appearance > Themes
  2. Backup the WordPress site including database and files
  3. Download Benevolent theme version 1.3.5 or later from a trusted source (official WordPress theme repository or vendor)
  4. Update the theme through WordPress admin: Appearance > Themes > Add New > Upload Theme, or replace via FTP/SFTP
  5. Verify the update was successful by checking the theme version number
  6. Clear any caching plugins and server-side caches

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

Fix this in Benevolent Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-37450 — 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-37450 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