CVE-2026-58029 MediaWiki Authentication Bypass
A vulnerability in MediaWiki's authentication handling allows attackers to compromise user account security. The flaw resides in how the software processes authentication-related API calls and account linking operations. An attacker can exploit this without authentication or user interaction to gain unauthorized access to user accounts or modify account credentials, though the vulnerability does not enable full system compromise or data destruction.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 6.5 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
- Weaknesses (CWE)
- CWE-287
- Affected products
- 2 configuration(s)
- Published / Modified
- 2026-07-01 / 2026-07-09
NVD description (verbatim)
Vulnerability in Wikimedia Foundation MediaWiki. This vulnerability is associated with program files includes/Api/ApiChangeAuthenticationData.Php, includes/Api/ApiLinkAccount.Php, includes/Api/ApiRemoveAuthenticationData.Php, includes/Specials/SpecialLinkAccounts.Php, includes/Specials/SpecialUnlinkAccounts.Php. This issue affects MediaWiki: from * before 1.46.0, 1.45.4, 1.44.6, 1.43.9.
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-58029 is an authentication bypass vulnerability (CWE-287) affecting MediaWiki's authentication data management. The vulnerability exists in five key components: ApiChangeAuthenticationData.php, ApiLinkAccount.php, ApiRemoveAuthenticationData.php, SpecialLinkAccounts.php, and SpecialUnlinkAccounts.php. The flaw permits an unauthenticated, remote attacker to modify or link authentication credentials without proper authorization checks. The CVSS 3.1 score of 6.5 (MEDIUM severity) reflects network accessibility and low attack complexity, with limited impact on confidentiality and integrity but no availability impact.
Business impact
This vulnerability could result in unauthorized account takeovers on MediaWiki installations, particularly concerning for organizations running wiki platforms for collaborative work, documentation, or community engagement. Attackers could read or modify sensitive wiki content, impersonate legitimate users, alter documentation, or inject malicious content. Organizations operating large or publicly-facing MediaWiki instances face reputational damage and potential data integrity issues, though the vulnerability's medium severity suggests it is not a critical infrastructure threat.
Affected systems
All versions of MediaWiki are affected except 1.46.0, 1.45.4, 1.44.6, and 1.43.9 (the patched releases). Any unpatched installation—whether self-hosted or managed—running versions prior to these patch releases is vulnerable. This includes legacy versions where patches may not be available, requiring administrators to plan upgrade paths carefully.
Exploitability
The vulnerability requires only network access and no authentication or user interaction, making it relatively straightforward to exploit. An attacker can trigger the flaw remotely by sending crafted requests to the affected API endpoints. However, the lack of active KEV listing suggests it is not currently weaponized in widespread attacks, though this does not diminish the need for timely patching.
Remediation
Upgrade MediaWiki immediately to one of the patched versions: 1.46.0 (latest stable), 1.45.4, 1.44.6, or 1.43.9 (LTS). Organizations unable to upgrade immediately should implement network-level controls to restrict access to the affected API endpoints (/api.php calls related to authentication) and monitor logs for suspicious authentication-related requests. Verify against vendor advisories for any additional mitigation steps specific to your deployment configuration.
Patch guidance
The Wikimedia Foundation has released patched versions addressing this issue. Administrators should prioritize upgrading to the latest stable release (1.46.0) or their supported LTS branch. Verify the version number post-patch using MediaWiki's version reporting feature (typically available in Special:Version). Test patches in a staging environment before deploying to production to ensure compatibility with extensions and local configurations. For organizations with custom authentication implementations, review any local modifications to the affected components.
Detection guidance
Monitor API logs for unusual patterns in requests to /api.php with actions like 'changeauthenticationdata', 'linkaccount', or 'removeauthenticationdata'. Alert on successful authentication changes from unexpected IP addresses or without corresponding user login sessions. Enable detailed logging on Special:LinkAccounts and Special:UnlinkAccounts pages. Review user account modification logs for unauthorized changes to authentication methods or linked accounts. Correlate failed authentication attempts with successful account changes in the same session window.
Why prioritize this
While rated MEDIUM severity, this vulnerability directly enables account compromise and affects a widely-used collaborative platform. Organizations operating MediaWiki should prioritize patching within 2–4 weeks based on their risk tolerance and whether the installation is internet-facing. The lack of known active exploitation provides a window for planned patching, but the ease of exploitation warrants urgent action.
Risk score, explained
The CVSS 3.1 score of 6.5 reflects a network-accessible vulnerability with no authentication barriers, resulting in moderate impact to confidentiality and integrity. The score does not account for business context—the ability to compromise user accounts and alter wiki content can be significant for organizations depending on wiki accuracy and user trust. Adjust internal risk ratings upward if your MediaWiki instance is public-facing, contains sensitive documentation, or supports critical workflows.
Frequently asked questions
Can this vulnerability be exploited without internet access?
No. The vulnerability requires network access to the affected MediaWiki API endpoints. Instances isolated on internal networks or restricted behind firewalls face lower immediate risk, though network segmentation should not be relied upon as a substitute for patching.
Will patching affect our custom authentication integrations?
Patching targets the core authentication handling components. If you have custom authentication extensions or local modifications to the affected files, test thoroughly in a staging environment first. Wikimedia's patch notes will clarify any breaking changes; review the security advisory for your specific version branch.
Do we need to force password resets after patching?
Verify the vendor advisory for specific guidance. If the flaw allowed account credential changes without authorization, post-patch password resets are prudent as a precautionary measure, particularly for accounts with elevated permissions. Review authentication logs to identify accounts that may have been compromised.
Is this vulnerability included in CISA's Known Exploited Vulnerabilities list?
No, as of publication, this vulnerability is not on CISA's KEV catalog and shows no evidence of active exploitation in the wild. This does not mean exploitation is impossible—only that it has not been widely observed. Continue monitoring threat intelligence feeds for any changes.
This analysis is provided for informational purposes and reflects the vulnerability details as of the published date. CVSS scores, patch version numbers, and affected versions are sourced from the official security advisory. Readers should verify all patch availability and version numbers directly against Wikimedia Foundation's security advisories before deploying patches. This assessment does not constitute legal or compliance advice; organizations should consult their internal security and compliance teams when prioritizing remediation. No exploit code or weaponized proof-of-concept is provided; security researchers and vendors should follow responsible disclosure practices. Source: NVD (public-domain), retrieved 2026-08-10. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2023-5502MEDIUMArista EOS 802.1x Authentication Bypass Vulnerability
- CVE-2026-10283MEDIUMBottelet DaybydayCRM Authentication Bypass in Settings Handler
- CVE-2026-10548MEDIUMImproper Authentication in NousResearch hermes-agent Credential Synchronization
- CVE-2026-13208MEDIUMKubeVirt virt-handler gRPC Identity Validation Flaw
- CVE-2026-13543MEDIUMDocumenso Google OAuth Authentication Bypass Vulnerability (CVSS 5.6)
- CVE-2026-14627MEDIUMNousResearch Hermes-Agent Discord Authentication Bypass Vulnerability
- CVE-2026-14714MEDIUMCowAgent 2.1.0 WeChat Authentication Bypass – Exploit, Patch & Mitigation
- CVE-2026-15192MEDIUMMissing Authentication in Mettle Sendportal APIv1 Webhooks