CVE-2025-32664: WordPress Nepali Date Utilities plugin <= 1.0.15 - CSRF to Stored XSS vulnerability
Cross-Site Request Forgery (CSRF) vulnerability in ashokbasnet Nepali Date Utilities nepali-date-utilities allows Stored XSS.This issue affects Nepali Date Utilities: from n/a through <= 1.0.15.
Security readout for executives and security teams
Plain-English summary
Nepali Date Utilities for WordPress has a CSRF issue that can lead to stored cross-site scripting. An attacker may trick a logged-in site administrator into performing an unintended action, causing malicious script to be stored in the site. This can affect confidentiality, integrity, and availability at a limited level.
Executive priority
Treat this as high priority for WordPress estates using this plugin, especially public sites with multiple administrators. Prioritize inventory and containment now because no fixed version is named in the provided sources.
Technical view
CVE-2025-32664 is a CSRF to stored XSS vulnerability in ashokbasnet Nepali Date Utilities, reported for versions through 1.0.15. CVSS 3.1 is 7.1 high, with network attack vector, low complexity, no attacker privileges, required user interaction, changed scope, and low CIA impact.
Likely exposure
Exposure is limited to WordPress sites with the Nepali Date Utilities plugin installed and enabled in an affected version. The source bundle does not identify affected CPEs, install counts, or hosting-specific exposure indicators.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source here confirms active exploitation. The practical risk depends on convincing a privileged WordPress user to interact with attacker-controlled content while authenticated.
Researcher notes
Evidence supports CSRF leading to stored XSS, but remediation detail is incomplete. The bundle says affected through 1.0.15, while the Patchstack URL slug references 1.0.13; verify vendor advisory details before final scoping.
Mitigation direction
Inventory WordPress sites for the Nepali Date Utilities plugin.
Disable the plugin if it is not business-critical.
Check vendor, WordPress.org, and Patchstack guidance for a fixed release.
Update promptly when an official fixed version is available.
Review administrator security awareness around CSRF and phishing paths.
Validation and detection
Confirm whether the plugin is installed and enabled on each WordPress site.
Compare installed plugin versions against the reported affected range through 1.0.15.
Review plugin settings and related content for unexpected stored scripts.
Check web application firewall or WordPress security logs for suspicious admin-originated changes.
Track vendor or Patchstack advisories for remediation status.
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.