CVE-2025-23804
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 Shiv Prakash Tiwari WP Service Payment Form With Authorize.net wp-service-payment-form-with-authorizenet allows Reflected XSS.This issue affects WP Service Payment Form With Authorize.net: from n/a through <= 2.6.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 · high confidenceCross-Site Request Forgery (CSRF) vulnerability in the WP Service Payment Form With Authorize.net WordPress plugin allows attackers to trick authenticated administrators into executing malicious requests that result in Reflected XSS. The lack of CSRF tokens on form actions enables attackers to craft malicious links that, when clicked by a logged-in admin, can inject arbitrary JavaScript into the response.
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 the plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP Service Payment Form With Authorize.net' or check the plugins directory for the plugin folder name containing 'authorize' and 'payment-form'Affected if The plugin is not found in the installed plugins list, so the vulnerability does not apply
-
Determine the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find the plugin, and read the version number from the plugin description. Compare this to the latest version available at wordpress.org/plugins/Affected if The installed version is older than the latest version available, indicating potential unpatched vulnerabilities
-
Verify the plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and confirm the plugin status shows 'Active'Affected if The plugin is active and handles form submissions from admin users, making the CSRF-to-Reflected XSS attack surface present
-
Check for form action endpointsExamine the plugin files (typically in wp-content/plugins/) for PHP files handling form submissions. Look for form tags with action attributes that process admin requests without checking for a CSRF token or nonceAffected if Form handling code exists without CSRF token validation (nonce checks), meaning the vulnerability is present in the current version
-
Confirm admin authentication requirementDetermine if the vulnerable form actions require administrator-level authentication by reviewing the plugin code or testing if unauthenticated requests to form endpoints are rejectedAffected if The forms require admin authentication but lack CSRF protection, allowing authenticated admins to be tricked into executing malicious requests
You are affected if the WP Service Payment Form With Authorize.net plugin is installed, active, handles form submissions, and lacks CSRF token validation on its admin-facing form actions.
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 dataUpdate to the latest version of the plugin when available. If no update exists, disable the plugin and implement manual anti-CSRF token validation plus proper input sanitization on all form handling endpoints.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23804 — 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-23804 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