CVE-2025-32068
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 · uneditedIncorrect Authorization vulnerability in The Wikimedia Foundation Mediawiki - OAuth Extension allows Authentication Bypass.This issue affects Mediawiki - OAuth Extension: from 1.39 through 1.43.
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 confidenceThe Mediawiki OAuth extension contains an incorrect authorization check that allows attackers to bypass authentication mechanisms. This enables unauthorized access to user accounts or resources protected by the OAuth extension in affected Mediawiki installations.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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.
-
Verify MediaWiki OAuth extension is installedCheck the MediaWiki installation directory for the OAuth extension files. Look for the 'OAuth' directory in 'extensions/' folder, or check LocalSettings.php for 'wfLoadExtension( "OAuth" )' or similar require statements.Affected if The OAuth extension directory exists and is loaded in MediaWiki configuration.
-
Determine OAuth extension versionCheck the version file in the OAuth extension directory, typically 'extension.json' or 'composer.json', or run 'composer show mediawiki/oauth' if using Composer.Affected if The installed version is at or below the version that received the security patch.
-
Confirm OAuth is enabled in MediaWiki configurationExamine LocalSettings.php for '$wgOAuthPermissions' or '$wgMWOAuthSecretKeys' settings, or check the Special:OAuth page is accessible.Affected if OAuth authentication is actively configured or enabled for user logins.
-
Check for consumer registration settingsLook for '$wgOAuthConsumers' configuration in LocalSettings.php or examine the database table 'oauth_consumer' if accessible.Affected if OAuth consumers are registered, indicating OAuth is in use as an authentication mechanism.
A user is affected if the MediaWiki OAuth extension is installed, enabled, and running at a version that does not include the corrected authorization logic.
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.
From vendor dataUpgrade the Mediawiki OAuth extension to a version beyond 1.43 that includes the patched authorization logic, or apply the official security patch if available for the affected version range.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32068 — 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-2025-32068 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