CVE-2025-32664
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 ashokbasnet Nepali Date Utilities nepali-date-utilities allows Stored XSS.This issue affects Nepali Date Utilities: from n/a through <= 1.0.15.
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 · moderate confidenceA CSRF vulnerability in the Nepali Date Utilities library (nepali-date-utilities, versions <=1.0.15) allows attackers to inject malicious scripts through Stored XSS by tricking users into making unintended requests to the application.
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.
-
Identify if Nepali Date Utilities library is usedSearch project files for 'nepali-date-utilities' in package.json, composer.json, requirements.txt, or similar dependency manifests. Also check node_modules, vendor, or other package directories for the library presence.Affected if The library is found as a direct or transitive dependency in the project.
-
Check installed library versionLocate the installed version from lock files (package-lock.json, yarn.lock, composer.lock) or by querying the package manager (npm list nepali-date-utilities, pip show, etc.). Compare the version to the affected range <=1.0.15.Affected if The installed version is 1.0.15 or lower.
-
Determine if application processes Nepali date input from untrusted sourcesReview application code for usage of the library's functions that accept user-supplied data (such as date parsing, formatting, or conversion functions). Check if HTTP request parameters, form inputs, API payloads, or external API responses feed into nepali-date-utilities functions.Affected if The application passes untrusted input to the library's date parsing or formatting functions without prior sanitization.
-
Inspect output handling for stored dataSearch code that renders or outputs data processed by the library. Look for places where Nepali date values are inserted into HTML, JSON responses, or other output streams without proper encoding.Affected if Nepali date data is rendered in responses without output encoding (HTML escaping, JSON encoding) that would neutralize script injection.
-
Check for CSRF protection on state-changing operationsReview if forms or API endpoints that use the Nepali Date Utilities library have CSRF token validation. Look for CSRF middleware, tokens in forms, or SameSite cookie attributes.Affected if State-changing operations lack CSRF token validation or SameSite cookie protection.
You are affected if the nepali-date-utilities library version is 1.0.15 or lower AND your application processes user input through it AND outputs the results without proper encoding and CSRF protection.
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 dataUpgrade to a patched version of the library that implements proper CSRF token validation and output encoding to prevent stored XSS attacks.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32664 — 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-32664 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