CVE-2025-32070
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 · uneditedImproper Input Validation vulnerability in The Wikimedia Foundation Mediawiki - AJAX Poll Extension allows Cross-Site Scripting (XSS).This issue affects Mediawiki - AJAX Poll Extension: from 1.39 through 1.43.
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 confidenceImproper input validation in the MediaWiki AJAX Poll Extension allows attackers to inject malicious scripts via poll inputs. The vulnerability stems from insufficient sanitization of user-submitted poll data before it's rendered, enabling stored XSS attacks against other users who view the poll.
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
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 AJAX Poll Extension is installedCheck your MediaWiki installation's extensions directory for the 'AjaxPoll' or 'AJAXPoll' folder, or look for 'wfLoadExtension( 'AjaxPoll' )' in your LocalSettings.php fileAffected if The extension folder exists and the extension is loaded in LocalSettings.php
-
Identify the installed extension versionOpen the extension's version file (usually extension.json, composer.json, or a VERSION file in the AjaxPoll directory) and note the version numberAffected if The version is 1.43 or earlier (the vulnerable range before proper input validation was implemented)
-
Verify poll functionality is in useCheck MediaWiki pages for any existing polls created using the AJAX Poll extension syntax (typically {{#ajaxpoll:...}} or similar parser function)Affected if Polls have been created and are accessible to users, meaning user-submitted data can be stored and rendered
-
Inspect poll input handling configurationReview the extension's source code in AjaxPoll_body.php or similar main files to see if output encoding functions (such as htmlspecialchars) are applied to poll question and option fields before renderingAffected if User-provided poll question and option text is rendered without proper HTML encoding or sanitization routines
A user is affected if the AJAX Poll Extension version 1.43 or earlier is installed and polls are active on the wiki, as malicious script can be injected through poll inputs and executed when other users view those polls.
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 the AJAX Poll Extension to a patched version beyond 1.43 that implements proper input validation and output encoding, or apply server-side input sanitization to all poll-related form fields before storage and rendering.
- 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-32070 — 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-32070 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