Security readout for executives and security teams
Plain-English summary
CVE-2025-46442 affects the WordPress Loan Calculator plugin, package repayment-calculator, through version 1.3. A malicious site could abuse a logged-in WordPress user’s browser to save harmful script into the site. That script could later run for site users or administrators, risking data exposure, content changes, and operational disruption.
Executive priority
Treat this as high priority for WordPress sites using the plugin. It is not proven exploited in the supplied sources, but stored XSS on public websites can affect trust, visitor safety, and administrative control.
Technical view
The issue is a CSRF vulnerability leading to stored XSS in Casey Johnson’s Loan Calculator plugin for WordPress. The CVSS 3.1 score is 7.1: network-reachable, low complexity, no attacker privileges, user interaction required, changed scope, and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to WordPress installations running Loan Calculator, package repayment-calculator, through version 1.3. The source bundle does not identify affected configurations beyond the plugin/version range.
Exploitation context
The CVE is not listed as KEV in the supplied data, and the provided sources do not state active exploitation. The attack model requires user interaction, consistent with CSRF, and can result in stored XSS.
Researcher notes
Evidence is narrow: the bundle identifies CSRF to stored XSS, affected versions through 1.3, CVSS 7.1, CWE-352, and one Patchstack reference. It does not provide exploit detail, fixed version, vulnerable endpoint, or confirmed exploitation.
Mitigation direction
Inventory WordPress sites for repayment-calculator or Loan Calculator plugin installations.
Prioritize sites running plugin version 1.3 or earlier.
Check Patchstack and vendor guidance for a confirmed fixed version or mitigation.
Disable or remove the plugin if no trusted fix is available.
Limit administrator sessions and review WordPress hardening controls.
Validation and detection
Confirm plugin presence and version across production WordPress sites.
Review administrative pages for unexpected stored script or injected markup.
Check recent content and plugin settings changes for unauthorized modifications.
Review security logs for suspicious admin-side requests or redirects.
Track CVE and Patchstack updates for fixed-version confirmation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-352 · source CWE mapping
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.