CVE-2026-13707 in MediaWiki OAuth
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.
Quick answer
Wikimedia Foundation MediaWiki OAuth should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- MediaWiki OAuth extension through 1.46.0, 1.45.4, 1.44.6, and 1.43.9
- 1.46.0
Fixed versions
- MediaWiki OAuth current master or relevant supported release branch with the July 2026 security backport
How to fix it
CVE-2026-13707 affects MediaWiki OAuth. Update MediaWiki or the affected extension to a supported fixed branch. Keep editing and admin access limited until the update is live.
- Find the MediaWiki site or extension that uses MediaWiki OAuth.
- Check if it matches MediaWiki OAuth extension through 1.46.0, 1.45.4, 1.44.6, and 1.43.9.
- Update to MediaWiki OAuth current master or relevant supported release branch with the July 2026 security backport.
- Back up the site and database before changing code.
- Clear caches after the update.
- Review logs for strange account, page, or admin activity.
- Remove old extension files that are no longer used.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the fixed MediaWiki or extension version is deployed.
- Test login, edit, and admin flows.
- Check that the issue cannot be repeated.
- Run a new Fixnx scan.
- Keep the Wikimedia or NVD advisory in the change record.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-13707?
Wikimedia Foundation MediaWiki OAuth versions listed as affected should be reviewed: MediaWiki OAuth extension through 1.46.0, 1.45.4, 1.44.6, and 1.43.9, 1.46.0.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.