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

CVE-2025-24712

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-24
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
Cross-Site Request Forgery (CSRF) vulnerability in RadiusTheme Radius Blocks radius-blocks allows Cross Site Request Forgery.This issue affects Radius Blocks: from n/a through <= 2.1.2.

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 Radius Blocks WordPress plugin (version <= 2.1.2). The flaw allows attackers to trick authenticated administrators into unknowingly submitting malicious requests to the application, potentially performing unauthorized actions such as modifying plugin settings or content.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing operations including form submissions and AJAX requests, and validate the HTTP Referer header to ensure requests originate from legitimate pages.

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
None
Integrity
Low
Availability
Low

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

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. Identify if Radius Blocks plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/radius-blocks/) or view the installed plugins list in the WordPress admin under Plugins
    Affected if The plugin directory exists in the WordPress installation
  2. Determine the installed version of Radius Blocks
    Open the main plugin file (radius-blocks.php) and check the Version header in the plugin comment block, or look in the WordPress admin plugin list
    Affected if The version is 2.1.2 or lower
  3. Examine plugin code for nonce implementation
    Search the plugin source files for wp_nonce_field, wp_nonce_url, check_admin_referer, or wp_verify_nonce function calls
    Affected if No nonce functions are found in form processing or AJAX handlers, or nonces are missing from state-changing operations
  4. Check form submissions for CSRF protection
    Review all PHP files that handle form submissions (settings pages, content modification) to verify each uses nonce verification before processing
    Affected if Forms submit data without validating a nonce token first
  5. Check AJAX handlers for CSRF protection
    Examine any AJAX action handlers in the plugin (look for wp_ajax_ hooks) to confirm they verify nonces before processing requests
    Affected if AJAX endpoints process requests without nonce validation

A user is affected if the Radius Blocks plugin version is 2.1.2 or lower and the plugin's state-changing operations lack proper nonce verification.

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

Implement anti-CSRF tokens (nonces) on all state-changing operations including form submissions and AJAX requests, and validate the HTTP Referer header to ensure requests originate from legitimate pages.

Recommended fix Moderate confidence

Latest available version of Radius Blocks (newer than 2.1.2)

  1. 1. Log in to the WordPress admin dashboard where the Radius Blocks plugin is installed
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Radius Blocks plugin in the plugin list
  4. 4. If an update is available, click 'Update Now' to update to the latest version
  5. 5. After updating, verify the plugin version in the plugins list to confirm the update was successful
  6. 6. Test critical functionality that uses Radius Blocks to ensure the update did not break any features
  7. 7. If no update is available from the WordPress plugin repository, download the latest version from the official WordPress plugin directory or contact RadiusTheme for the patched release
Caveat Minimal risk - plugin updates typically maintain backward compatibility, but test in staging first if possible

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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