CVE-2025-23861
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 Zack Katz Debt Calculator debt-calculator allows Cross Site Request Forgery.This issue affects Debt Calculator: from n/a through <= 1.0.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 Debt Calculator WordPress plugin versions through 1.0.1 allows attackers to induce authenticated users to perform unintended state-changing actions via malicious requests, with CVSS 7.1 indicating high severity due to the ability to manipulate user sessions.
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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Debt Calculator plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and search for 'Debt Calculator', or check the /wp-content/plugins/ directory for a debt-calculator folderAffected if The Debt Calculator plugin is present in the WordPress installation
-
Identify the installed plugin versionIn Plugins page, click 'View Details' on Debt Calculator plugin to display the version number, or read version from the plugin's main PHP file headerAffected if The version is 1.0.1 or any version below 1.0.1 (the vulnerability affects through version 1.0.1)
-
Verify if state-changing forms lack nonce protectionExamine the plugin's PHP files for form handlers and AJAX callbacks. Search for 'wp_nonce_field', 'wp_verify_nonce', or 'check_ajax_referer' functions. Check if forms generating state-changing requests (settings changes, data submissions) include nonce tokensAffected if State-changing forms or AJAX endpoints do not implement nonce verification (no wp_nonce_field or wp_verify_nonce calls found)
-
Check for Origin/Referer header validationReview plugin PHP code for server-side validation of $_SERVER['HTTP_ORIGIN'] or $_SERVER['HTTP_REFERER'] headers before processing state-changing requestsAffected if No Origin or Referer header validation is performed before processing sensitive operations
You are affected if the Debt Calculator plugin is installed with version 1.0.1 or below AND the plugin's state-changing operations lack anti-CSRF nonce validation on forms or AJAX endpoints.
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 anti-CSRF tokens (nonces) on all state-changing operations (forms, AJAX endpoints), validate Origin/Referer headers, and set SameSite attribute on session cookies to prevent cross-site request forgery attacks.
- 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-23861 — 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-23861 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