CVE-2025-23656
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 · uneditedMissing Authorization vulnerability in Saul Morales Pacheco Donate visa donate-visa allows Stored XSS.This issue affects Donate visa: from n/a through <= 1.0.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 confidenceMissing authorization in the Donate visa plugin (versions <= 1.0.0) allows attackers to inject malicious JavaScript through the donation form, resulting in Stored XSS. Without proper authorization checks, unauthenticated or low-privilege users can submit crafted payloads that persist and execute when administrators or other users view donation records.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm Donate visa plugin is installedNavigate to the WordPress admin plugin list or check the wp-content/plugins directory for a folder named 'donate-visa' or similar. Look for a plugin with 'donate' and 'visa' in the name.Affected if The plugin folder exists in the plugins directory and the plugin is activated.
-
Identify the installed plugin versionOpen the main plugin PHP file (usually plugin-name.php in the plugin folder) and locate the version defined in the plugin header comment (e.g., 'Version: 1.0.0'). Compare this to the affected range of versions <= 1.0.0.Affected if The version is 1.0.0 or lower.
-
Verify donation form functionality existsAccess the frontend of the site and look for a donation form related to the plugin. Check the plugin settings page in the admin dashboard to confirm donation submissions are enabled.Affected if A donation form is present and accepting submissions on the site.
-
Inspect stored donation records for lack of output encodingUse a database query or the plugin admin interface to view stored donation submissions. Check the HTML source of how these records are rendered in the admin dashboard to see if user-supplied fields (name, amount, message) are being output without encoding.Affected if Donation records can be viewed in the admin panel and user-supplied fields appear to render raw or unescaped content.
If the Donate visa plugin version is 1.0.0 or lower, the plugin is active, and donation submissions are being stored and displayed in the admin area without escaping, the environment is vulnerable to CVE-2025-23656.
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 dataAdd role-based capability checks and nonce verification before processing donation submissions. Implement output escaping for all user-supplied data displayed in the admin dashboard and frontend.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23656 — 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-23656 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