CVE-2025-46442
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 Casey Johnson Loan Calculator repayment-calculator allows Stored XSS.This issue affects Loan Calculator: from n/a through <= 1.3.
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 vulnerability in the Loan Calculator plugin enables attackers to inject malicious JavaScript through form fields. The lack of CSRF protection allows attackers to craft requests that inject XSS payloads into stored data, which then executes when other users view the calculator.
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 Loan Calculator plugin is installedCheck your site's plugin directory or WordPress plugin list for the Loan Calculator plugin and note its version if displayedAffected if The Loan Calculator plugin is installed and active on the site
-
Inspect form HTML for CSRF tokensView the source of any form rendered by the Loan Calculator plugin. Look for input fields named 'nonce', '_wpnonce', 'token', or similar security tokensAffected if No anti-CSRF token fields are present in the plugin's forms
-
Review form handling code for nonce verificationExamine the plugin's PHP code that processes form submissions. Look for calls to verify_nonce, wp_verify_nonce, or check_admin_referer functionsAffected if Form submission handlers do not verify CSRF tokens before processing input
-
Check input sanitization on form fieldsReview the plugin code that handles form input. Look for sanitization functions like sanitize_text_field, esc_attr, or similar cleaning functions applied to user inputAffected if Form input processing lacks sanitization functions for the fields that accept user data
-
Verify output encoding when displaying stored dataExamine how the calculator displays saved data. Look for escaping functions like esc_html, esc_attr, or htmlspecialchars when outputting stored valuesAffected if Stored data is output without proper encoding/escaping, allowing raw data to render in the browser
Your environment is affected if the Loan Calculator plugin is installed and its forms lack CSRF token fields and proper sanitization/encoding of user input.
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 forms and add proper input sanitization plus output encoding to prevent stored XSS. Also consider implementing Content Security Policy headers.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46442 — 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-46442 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