CVE-2025-53485
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 · uneditedSetTranslationHandler.php does not validate that the user is an election admin, allowing any (even unauthenticated) user to change election-related translation text. While partially broken in newer MediaWiki versions, the check is still missing. This issue affects Mediawiki - SecurePoll extension: from 1.39.X before 1.39.13, from 1.42.X before 1.42.7, from 1.43.X before 1.43.2.
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 confidenceThe SecurePoll extension's SetTranslationHandler.php endpoint lacks an authorization check to verify the user has election admin privileges. This allows any requester, including unauthenticated users, to modify election-related translation text by directly calling the handler, constituting a broken access control vulnerability.
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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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.
-
Verify SecurePoll extension is installedCheck the MediaWiki extensions directory for the SecurePoll folder, or look for 'wfLoadExtension( 'SecurePoll' )' in LocalSettings.phpAffected if SecurePoll extension is present and enabled in MediaWiki
-
Identify the installed SecurePoll versionCheck the extension's version file (usually in includes/ SecurePoll.php or SpecialSecurePoll.php) or look at the version number in the composer.json or extension.json file within the SecurePoll directoryAffected if Version is below 1.39.13, 1.42.7, or 1.43.2, or if the version cannot be determined (likely vulnerable)
-
Confirm SetTranslationHandler.php existsLocate the file SetTranslationHandler.php within the SecurePoll extension directory (typically in includes/handlers/ or similar subdirectory)Affected if The file exists in the installation, meaning the vulnerable endpoint is present
-
Check if the translation handler endpoint is accessibleAttempt a POST request to the SetTranslationHandler endpoint (usually at /wiki/Special:SecurePoll/set-translation or similar URL pattern). If the server accepts the request without requiring election admin authentication, the vulnerability is present.Affected if The endpoint accepts and processes requests without verifying user has election admin privileges
If SecurePoll is installed and its version is lower than 1.39.13, 1.42.7, or 1.43.2, the installation is affected by this missing authorization check.
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.
dbcve · scopedUpgrade MediaWiki SecurePoll to version 1.39.13, 1.42.7, or 1.43.2 which contain the missing election admin authorization check in SetTranslationHandler.php.
SecurePoll 1.39.13 (for 1.39.x users), 1.42.7 (for 1.42.x users), or 1.43.2 (for 1.43.x users)
- Identify the current version of the SecurePoll extension by checking the extension's version file or composer.json
- Determine which release branch (1.39, 1.42, or 1.43) is currently installed
- If running 1.39.x: upgrade SecurePoll to version 1.39.13 or later
- If running 1.42.x: upgrade SecurePoll to version 1.42.7 or later
- If running 1.43.x: upgrade SecurePoll to version 1.43.2 or later
- Upgrade can be performed via composer update wikimedia/securepoll or by pulling the updated extension from the MediaWiki repository
- Clear any relevant caches after upgrading
- Verify the authorization check is now present in SetTranslationHandler.php by confirming the code includes an election admin permission check before processing translation changes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53485 — 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-53485 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