CVE-2025-23872
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 payform PayForm payform allows Stored XSS.This issue affects PayForm: from n/a through <= 2.0.
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 PayForm allows attackers to craft malicious requests that result in Stored XSS. Since the application lacks proper anti-CSRF tokens on forms, an attacker can trick an authenticated admin into submitting a form that injects malicious scripts into the application, which are then stored and executed when other users view the affected content.
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 PayForm installation and versionLocate PayForm application files (e.g., form builder, payment form scripts). Check for version identifiers in source files, configuration files, or HTTP response headers. Compare your installed version to the affected version range.Affected if The installed version falls within the vulnerable version range and no patches have been applied.
-
Inspect forms for anti-CSRF tokensView the HTML source of forms in PayForm (login, registration, payment, admin forms). Look for hidden input fields containing random tokens (e.g., <input type='hidden' name='csrf_token'>) or custom CSRF headers in the form markup.Affected if Forms lack anti-CSRF token fields or the tokens are not being generated/validated server-side.
-
Check form submission endpoints for CSRF validationReview server-side code that handles form submissions (e.g., PHP, Python, Node.js handlers). Verify that incoming requests validate the presence and correctness of CSRF tokens before processing state-changing operations.Affected if Form handlers do not validate CSRF tokens or skip validation under certain conditions.
-
Test for stored XSS via form injectionSubmit a test payload (e.g., <script>alert('XSS')</script>) through forms while authenticated as admin. Then access the stored content as a different user to see if the script executes without sanitization.Affected if Injected script content is rendered unescaped in the browser when viewed by other users.
You are affected if PayForm is running a vulnerable version AND forms lack anti-CSRF tokens AND stored content renders unsanitized JavaScript.
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 on all state-changing forms and apply proper input validation and output encoding to prevent XSS. Review form submission handlers to ensure they validate the origin of requests.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23872 — 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-23872 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