Dofollow Case By CaseWordPress extension · Apasionados
CVE-2025-47624
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in apasionados DoFollow Case by Case dofollow-case-by-case allows Cross Site Request Forgery.This issue affects DoFollow Case by Case: from n/a through <= 3.5.1.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the WordPress plugin 'DoFollow Case by Case' by apasionados. The plugin fails to properly validate anti-CSRF tokens on state-changing requests, allowing attackers to trick authenticated administrators into performing unintended actions such as modifying plugin settings or case configurations.
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
Dofollow Case By CaseWordPress extension
<= 3.5.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and locate 'DoFollow Case by Case' (Apasionados) to view the version number. Alternatively, check the plugin's main PHP file or readme.txt for the Version header.Affected if The installed version is 3.5.1 or lower.
-
Inspect plugin PHP files for nonce implementationAccess the plugin directory via FTP or file manager. Open the main plugin PHP files (typically named 'dofollow-case-by-case.php' or similar) and search for 'wp_nonce_field', 'wp_nonce_url', 'check_admin_referer', or 'wp_verify_nonce'.Affected if No nonce verification functions are found in the plugin code, or state-changing functions lack nonce checks.
-
Check form submissions for CSRF tokensActivate the plugin and navigate to its settings pages. View the page source (right-click > View Page Source) and examine any forms generated by the plugin for hidden nonce fields (input type='hidden' name='_wpnonce').Affected if Forms that modify plugin settings or dofollow configurations lack hidden nonce fields.
-
Examine AJAX actions for nonce validationReview the plugin's PHP files for add_action('wp_ajax_') calls. Verify that each AJAX handler includes nonce verification (wp_verify_nonce or check_admin_referer) before processing the request.Affected if AJAX endpoints that change plugin state do not validate nonce tokens.
-
Check for Origin/Referer header validationSearch the plugin's PHP files for server-side checks of $_SERVER['HTTP_REFERER'] or $_SERVER['HTTP_ORIGIN'] when processing form submissions or AJAX requests.Affected if No referer or origin header validation exists in the plugin's request handlers.
You are affected if the installed version is 3.5.1 or lower AND the plugin lacks nonce verification on its state-changing forms, AJAX actions, or settings updates.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement WordPress nonces (wp_nonce_field/check_admin_referer) on all forms and AJAX actions that modify plugin state. Update to the latest patched version when available.
Fix this in Dofollow Case By Case
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-47624 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-47624 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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