dbcve.org
MediawikiCMS

CVE-2026-58518

MEDIUM · 6.3 CVSS v3.1 Published 2026-07-01
Fix available
A fix is available. Upgrade to 1.3.3 or later.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable No privileges 7 weeks old

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
Cross-Site request forgery (CSRF) vulnerability in The Wikimedia Foundation Mediawiki - RedirectManager Extension allows Cross Site Request Forgery. This issue affects Mediawiki - RedirectManager Extension: from * before 1.3.3.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in Mediawiki's RedirectManager Extension allows attackers to induce authenticated users to perform unintended actions (such as creating, modifying, or deleting redirects) via maliciously crafted requests. The lack of anti-CSRF tokens in the affected versions enables attackers to exploit the trust relationship between the authenticated user and the application.

MitigationUpgrade the RedirectManager Extension to version 1.3.3 or later, which includes anti-CSRF token validation. If immediate patching is not possible, consider disabling the extension or implementing web application firewall rules to block malicious request patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MediawikiCMS
Affected:< 1.3.3

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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 checks

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

  1. Verify RedirectManager extension is installed
    Check your MediaWiki installation for the presence of the RedirectManager extension in the /extensions/RedirectManager/ directory, or query Special:Version in your wiki to list installed extensions.
    Affected if The RedirectManager extension appears in your list of installed extensions.
  2. Determine RedirectManager extension version
    Locate the extension.json or composer.json file within the RedirectManager extension directory and read the version number, or view the extension version listed on MediaWiki's Special:Version page.
    Affected if The extension version shown is less than 1.3.3 (for example, 1.3.2, 1.3.0, or any version before 1.3.3).
  3. Confirm anti-CSRF token validation is missing
    Inspect the PHP source files in the RedirectManager extension (particularly the main entry point and any action handlers) and search for CSRF token validation logic using functions such as $this->getCsrfTokenSet(), $wgRequest->getCSRFToken(), or similar anti-CSRF token checks.
    Affected if The extension code contains no CSRF token validation before processing redirect creation, modification, or deletion requests.

Your environment is affected if the RedirectManager extension is installed with a version lower than 1.3.3 and lacks anti-CSRF token validation in its request handling code.

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
Upgrade available Upgrade to 1.3.3 or later
Fixed in 1.3.3
Interim mitigation

Upgrade the RedirectManager Extension to version 1.3.3 or later, which includes anti-CSRF token validation. If immediate patching is not possible, consider disabling the extension or implementing web application firewall rules to block malicious request patterns.

Recommended fix Moderate confidence

RedirectManager Extension version 1.3.3

  1. 1. Identify all Mediawiki installations using the RedirectManager Extension with version less than 1.3.3
  2. 2. Review the Mediawiki extension compatibility matrix to ensure version 1.3.3 is compatible with your Mediawiki core version
  3. 3. Backup your Mediawiki database and configuration files before proceeding
  4. 4. Upgrade the RedirectManager Extension to version 1.3.3 or later using your extension installation method (e.g., composer, git clone, or wiki interface)
  5. 5. Clear any caching systems (e.g., parser cache, object cache) after upgrade
  6. 6. Verify the extension is now reporting version 1.3.3 or later in Special:Version
  7. 7. Test the redirect functionality to ensure the extension operates correctly after the upgrade

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

Fix this in Mediawiki Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-58518 — 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-2026-58518 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