dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-53483

HIGH · 8.8 CVSS v3.1 Published 2025-07-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
ArchivePage.php, UnarchivePage.php, and VoterEligibilityPage#executeClear() do not validate request methods or CSRF tokens, allowing attackers to trigger sensitive actions if an admin visits a malicious site. 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 confidence

Cross-site request forgery (CSRF) vulnerability in MediaWiki SecurePoll extension where ArchivePage.php, UnarchivePage.php, and VoterEligibilityPage#executeClear() fail to validate request methods or CSRF tokens. Attackers can trick authenticated administrators into unknowingly triggering sensitive actions (archiving/unarchiving pages, clearing voter eligibility) via maliciously crafted requests.

MitigationImplement CSRF token validation (MediaWiki's $wgCsrfTokenSecret or similar) on all state-changing operations and enforce proper HTTP method restrictions (POST only) for these sensitive endpoints.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify SecurePoll extension is installed
    Locate the SecurePoll extension directory in your MediaWiki installation (typically at /extensions/SecurePoll/ or similar). Check for the presence of ArchivePage.php, UnarchivePage.php, and files containing VoterEligibilityPage.
    Affected if The SecurePoll extension is present and these specific PHP files exist in the installation.
  2. Identify the SecurePoll version
    Open the SecurePoll extension's composer.json, extension.json, or VERSION file (usually in the extension root directory) to find the installed version number.
    Affected if The installed version falls within the range of versions affected by CVE-2025-53483 (compare your version to the known vulnerable range).
  3. Inspect ArchivePage.php for CSRF protection
    Open includes/pages/ArchivePage.php in the SecurePoll extension directory. Search for CSRF token validation logic (look for 'getCsrfTokenSet', 'checkCsrfToken', 'validateToken', or similar function calls) and verify that POST method is required before any archive operation executes.
    Affected if The file lacks CSRF token validation or allows GET requests to trigger archive actions.
  4. Inspect UnarchivePage.php for CSRF protection
    Open includes/pages/UnarchivePage.php in the SecurePoll extension directory. Look for CSRF token validation and HTTP method enforcement (POST requirement) similar to the ArchivePage.php check.
    Affected if The file lacks CSRF token validation or allows GET requests to trigger unarchive actions.
  5. Inspect VoterEligibilityPage#executeClear() for CSRF protection
    Locate the file containing VoterEligibilityPage class (typically in includes/pages/ or similar). Find the executeClear() method and verify it validates CSRF tokens and requires POST method before clearing voter eligibility data.
    Affected if The executeClear() method lacks CSRF token validation or does not enforce POST-only requests.

You are affected if the SecurePoll extension is installed, your version is within the vulnerable range, and any of the three components (ArchivePage.php, UnarchivePage.php, or VoterEligibilityPage#executeClear) lack proper CSRF token validation and POST method enforcement.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement CSRF token validation (MediaWiki's $wgCsrfTokenSecret or similar) on all state-changing operations and enforce proper HTTP method restrictions (POST only) for these sensitive endpoints.

Recommended fix High confidence

SecurePoll 1.39.13 (for 1.39.X) / 1.42.7 (for 1.42.X) / 1.43.2 (for 1.43.X)

  1. 1. Identify the currently installed SecurePoll extension version in your MediaWiki installation
  2. 2. Determine which branch you are on (1.39.X, 1.42.X, or 1.43.X)
  3. 3. Download the appropriate fixed version from MediaWiki's extension repository (1.39.13 for 1.39.X, 1.42.7 for 1.42.X, or 1.43.2 for 1.43.X)
  4. 4. Backup your current SecurePoll extension directory and database
  5. 5. Replace the existing SecurePoll extension files with the new version
  6. 6. Run any database migration scripts if required by the upgrade
  7. 7. Clear MediaWiki caches to ensure the new code is loaded
  8. 8. Verify the extension is working correctly by testing poll creation and management functions

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-53483 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-53483 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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