dbcve.org
CreateredirectApplication · Mediawiki

CVE-2022-29547

HIGH · 7.5 CVSS v3.1 Published 2022-04-21
Fix available
A fix is available. Upgrade to 2022-04-14 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
The CreateRedirect extension before 2022-04-14 for MediaWiki does not properly check whether the user has permissions to edit the target page. This could lead to an unauthorised (or blocked) user being able to edit a page.

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

The CreateRedirect extension for MediaWiki versions before 2022-04-14 fails to verify that users have proper permissions to edit the target page before creating a redirect. This authorization bypass allows unauthorized or blocked users to potentially edit restricted pages through the redirect creation mechanism.

MitigationUpgrade the CreateRedirect extension to the version released on or after 2022-04-14 which includes proper permission checking, or apply the security patch that validates user edit permissions on the target page before allowing redirect creation.

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
CreateredirectApplication
Affected:< 2022-04-14

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 checks

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

  1. Locate the CreateRedirect extension directory
    Check your MediaWiki extensions folder (usually /extensions/CreateRedirect or similar) for the presence of the CreateRedirect extension files.
    Affected if The CreateRedirect extension directory exists in your MediaWiki installation.
  2. Identify the extension version or release date
    Look for a version file, composer.json, or the extension's main PHP file and check the version number or release date stamp against the 2022-04-14 threshold.
    Affected if The installed version is dated before 2022-04-14 or the version number is lower than the fixed release.
  3. Verify the extension is enabled
    Check your LocalSettings.php file for a line like 'wfLoadExtension( 'CreateRedirect' )' or similar enablement call.
    Affected if The extension is enabled in LocalSettings.php.
  4. Review user group permissions for redirect creation
    Examine $wgGroupPermissions in LocalSettings.php or the extension's configuration for any settings controlling who can create redirects (such as 'createredirect' or 'createredirect' rights).
    Affected if The permission configuration allows users without full edit rights to the target page to create redirects.

You are affected if the CreateRedirect extension is installed, enabled, and dated before 2022-04-14, allowing users who lack edit permissions on target pages to still create redirects to those pages.

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 2022-04-14 or later
Fixed in 2022-04-14
Interim mitigation

Upgrade the CreateRedirect extension to the version released on or after 2022-04-14 which includes proper permission checking, or apply the security patch that validates user edit permissions on the target page before allowing redirect creation.

Recommended fix Moderate confidence

Update to CreateRedirect extension version released on or after 2022-04-14

  1. 1. Identify the current version of the CreateRedirect extension installed in your MediaWiki installation
  2. 2. Navigate to your MediaWiki extensions directory and locate the CreateRedirect extension
  3. 3. Check the extension's version or changelog to verify it was released on or after 2022-04-14
  4. 4. If the installed version is older than 2022-04-14, update the extension to the latest available version from the MediaWiki extension repository
  5. 5. After updating, clear any cache and verify the extension functions correctly
  6. 6. Test that the permission checking now properly validates user rights before allowing edits to target pages

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

Fix this in Createredirect Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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