CVE-2025-32619
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 KeyCAPTCHA KeyCAPTCHA keycaptcha allows Stored XSS.This issue affects KeyCAPTCHA: from n/a through <= 2.5.1.
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 confidenceCSRF vulnerability in KeyCAPTCHA plugin <= 2.5.1 enables attackers to inject malicious scripts that get stored on the server (Stored XSS). When other users view the affected pages, the persistent malicious script executes in their browsers, potentially stealing session cookies or performing actions on behalf of authenticated users.
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.
-
Locate KeyCAPTCHA plugin installationSearch for KeyCAPTCHA plugin files in your CMS/plugin directory (common paths: /wp-content/plugins/ for WordPress, /sites/all/modules/ for Drupal, or the respective plugin folder of your CMS)Affected if KeyCAPTCHA plugin files are found in the system
-
Determine installed KeyCAPTCHA versionOpen the main plugin file (often keycaptcha.php, keycaptcha.php, or similar) and locate the version constant or header comment (e.g., 'Version: 2.5.1')Affected if The version is 2.5.1 or lower
-
Check if plugin is actively enabledAccess your CMS admin panel and verify KeyCAPTCHA is enabled in the plugin settings or configuration areaAffected if The plugin is enabled and actively processing CAPTCHA requests
-
Verify state-changing operations lack CSRF protectionExamine the plugin source code for form submissions or admin actions (typically POST handlers) and check if they include CSRF tokens or validation (look for token validation functions, nonce checks, or synchronizer token pattern)Affected if State-changing actions (saving settings, updating configurations) do not validate CSRF tokens
You are affected if KeyCAPTCHA plugin version 2.5.1 or lower is installed and enabled, and the plugin lacks CSRF token validation on its administrative 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 dataImplement CSRF tokens/synchronizer token pattern on all state-changing operations in KeyCAPTCHA; validate the origin and referer headers; update to patched version when available; consider disabling the plugin if no fix is released.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32619 — 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-32619 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