dbcve.org
FedoraOperating system · Fedoraproject

CVE-2022-34912

MEDIUM · 6.1 CVSS v3.1 Published 2022-07-02
Fix available
A fix is available. Upgrade to 1.37.3 or later.
See remediation →
68/100
Remediation priority · Elevated
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
An issue was discovered in MediaWiki before 1.37.3 and 1.38.x before 1.38.1. The contributions-title, used on Special:Contributions, is used as page title without escaping. Hence, in a non-default configuration where a username contains HTML entities, it won't be escaped.

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

A reflected XSS vulnerability exists in MediaWiki's Special:Contributions page where the contributions-title parameter is not properly escaped before being used as the page title. When a username contains HTML entities in a non-default configuration, these entities are rendered without encoding, allowing script injection.

MitigationUpgrade to MediaWiki 1.37.3 or 1.38.1 or later, which includes proper HTML escaping of the contributions-title parameter.

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
FedoraOperating system
Affected:= 36= 37
MediawikiCMS
Affected:< 1.37.3= 1.38.0

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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

  1. Identify MediaWiki installation version
    Check the MediaWiki version by visiting Special:Version on the wiki, or by examining the includes/Defines.php file for the MW_VERSION constant
    Affected if The installed version is less than 1.37.3, or exactly 1.38.0
  2. Verify access to Special:Contributions
    Confirm the Special:Contributions page is accessible by navigating to the wiki's /wiki/Special:Contributions endpoint
    Affected if The page is accessible and functional
  3. Test the contributions-title parameter
    Submit a request to Special:Contributions with a contributions-title parameter containing a test string such as contributions-title=<script>alert(1)</script> and observe if the parameter value is reflected unescaped in the response
    Affected if The HTML or script tags in the contributions-title parameter are rendered without encoding in the page output

A user is affected if their MediaWiki version is below 1.37.3 or exactly 1.38.0 AND the Special:Contributions page reflects the contributions-title parameter without proper HTML escaping.

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.37.3 or later
Fixed in 1.37.3
Interim mitigation

Upgrade to MediaWiki 1.37.3 or 1.38.1 or later, which includes proper HTML escaping of the contributions-title parameter.

Recommended fix High confidence

MediaWiki 1.37.3+ or 1.38.1+ (latest stable in respective branch)

  1. 1. Backup your MediaWiki database and files before proceeding
  2. 2. Download MediaWiki 1.37.3 or later (for the 1.37.x branch), or MediaWiki 1.38.1 or later (for the 1.38.x branch) from the official MediaWiki download page
  3. 3. Extract the new version to a temporary directory
  4. 4. Replace the existing MediaWiki core files with the new version, preserving your LocalSettings.php configuration file
  5. 5. Run the update.php maintenance script if required: php maintenance/update.php
  6. 6. Clear any caching systems (e.g., PHP opcache, MediaWiki object cache)
  7. 7. Verify the fix by checking Special:Contributions with a username containing HTML entities to confirm proper escaping
Caveat Minimal risk - this is a security fix for XSS escaping; review release notes for any deprecation warnings in your minor version jump

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

Fix this in Fedora Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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