dbcve.org
MediawikiCMS

CVE-2026-13707

HIGH · 7.6 CVSS v3.1 Published 2026-07-01
Fix available
A fix is available. Upgrade to 1.43.9 / 1.44.6 or later.
See remediation →
80/100
Remediation priority · High
Remotely reachable 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
Session fixation vulnerability in Wikimedia Foundation OAuth. This vulnerability is associated with program files src/Backend/MWOAuthServer.Php. This issue affects OAuth: from * through 1.46.0, 1.45.4, 1.44.6, 1.43.9.

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

Session fixation vulnerability in Wikimedia Foundation's OAuth implementation. An attacker can potentially set or predetermine a user's session ID before authentication, then hijack the authenticated session by using the fixed session ID. The vulnerability exists in the OAuth server code (MWOAuthServer.php) and affects versions through 1.46.0, 1.45.4, 1.44.6, and 1.43.9.

MitigationRegenerate session IDs immediately after successful OAuth authentication to prevent session fixation attacks. Update to a patched version of the Wikimedia OAuth extension if available.

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.43.0, < 1.43.9>= 1.44.0, < 1.44.6>= 1.45.0, < 1.45.4= 1.46.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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/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. Check MediaWiki version
    Run the command 'php maintenance/run.php showVersion' or check the file 'includes/Defines.php' for the $wgVersion variable
    Affected if The installed version is >= 1.43.0 and < 1.43.9, OR >= 1.44.0 and < 1.44.6, OR >= 1.45.0 and < 1.45.4, OR equals 1.46.0
  2. Verify OAuth extension is enabled
    Check your LocalSettings.php for the line 'wfLoadExtension( "OAuth" );' or look for 'OAuth' in the output of 'php maintenance/run.php listExtensions'
    Affected if The OAuth extension is loaded and enabled in the MediaWiki installation
  3. Confirm OAuth server functionality is in use
    Inspect your LocalSettings.php for $wgOAuthServers or check the database table 'oauth_registered_consumer' for registered OAuth consumers with server-enabled grants
    Affected if OAuth server functionality is configured and active on the wiki
  4. Check for session regeneration after OAuth auth
    Examine the MWOAuthServer.php file in your installation (typically in extensions/OAuth/includes/) for session_id regeneration calls following successful authentication
    Affected if The code lacks proper session ID regeneration after OAuth authentication completes

A user is affected if they run a MediaWiki version in the listed ranges and have the OAuth extension enabled with server functionality configured.

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.43.9 / 1.44.6 / 1.45.4 or later
Fixed in 1.43.91.44.61.45.4
Interim mitigation

Regenerate session IDs immediately after successful OAuth authentication to prevent session fixation attacks. Update to a patched version of the Wikimedia OAuth extension if available.

Recommended fix High confidence

1.46.1 (or 1.45.4/1.44.6/1.43.9 depending on your branch)

  1. 1. Backup your MediaWiki database and files before proceeding
  2. 2. Ensure you have a complete backup of the OAuth extension configuration
  3. 3. Upgrade MediaWiki to version 1.46.1 (recommended) or at minimum to your branch's fixed release: 1.43.9, 1.44.6, or 1.45.4
  4. 4. Clear any PHP OPcode caches (e.g., APC, OPcache) if enabled
  5. 5. Clear MediaWiki object caches (e.g., Redis, Memcached) if used
  6. 6. Verify the upgrade by logging in via OAuth and confirming session handling works correctly
  7. 7. Review the MediaWiki OAuth configuration for any session-related settings that may need adjustment
Caveat Minor: Review OAuth extension release notes for any configuration changes; standard minor upgrade risks apply

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

Fix this in Mediawiki Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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