FedoraOperating system · Fedoraproject
CVE-2022-34911
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 · uneditedAn issue was discovered in MediaWiki before 1.35.7, 1.36.x and 1.37.x before 1.37.3, and 1.38.x before 1.38.1. XSS can occur in configurations that allow a JavaScript payload in a username. After account creation, when it sets the page title to "Welcome" followed by the username, the username is not escaped: SpecialCreateAccount::successfulAction() calls ::showSuccessPage() with a message as second parameter, and OutputPage::setPageTitle() uses text().
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 confidenceCross-site scripting (XSS) vulnerability in MediaWiki's account creation flow. When a new user account is created, the username is displayed in the 'Welcome' page title without proper HTML escaping, allowing execution of malicious JavaScript via a crafted username payload.
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
= 36= 37< 1.35.7>= 1.36.0, < 1.37.3= 1.38.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed MediaWiki versionLocate the MediaWiki version file (typically includes/Defines.php or via Special:Version on the web interface, or 'php maintenance/showVersion.php' from command line)Affected if Version is < 1.35.7, OR >= 1.36.0 and < 1.37.3, OR = 1.38.0
-
Confirm MediaWiki is running on FedoraCheck if the MediaWiki instance is hosted on a Fedora 36 or 37 system using 'cat /etc/fedora-release'Affected if Running on Fedora 36 or 37 (which ship with vulnerable MediaWiki packages)
-
Verify account creation is enabledCheck LocalSettings.php for $wgGroupPermissions['*']['createaccount'] = true; or visit Special:Version to confirm account creation functionality is activeAffected if Account creation is enabled ($wgGroupPermissions['*']['createaccount'] is true or not explicitly disabled)
The environment is affected if MediaWiki version falls within the vulnerable ranges AND account creation is enabled, allowing a malicious username to trigger XSS in the welcome page title.
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 · scoped1.35.71.37.3
Upgrade to MediaWiki version 1.35.7, 1.37.3, 1.38.1 or later which contains the fix for proper username escaping in the welcome page title.
MediaWiki 1.35.7, 1.37.3, or 1.38.1 (depending on your current branch)
- Upgrade MediaWiki to version 1.35.7 or later for the 1.35.x branch
- Upgrade MediaWiki to version 1.37.3 or later for the 1.36.x or 1.37.x branch
- Upgrade MediaWiki to version 1.38.1 or later for the 1.38.x branch
- For Fedora systems, run 'dnf update mediawiki' or 'dnf update' to receive the package security fix
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fedora
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34911 — 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-2022-34911 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