Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister lookalike Wikimedia-suffix domain
-
DeliveryLure user to attacker URL in app
-
ExploitApp matches domain via loose endsWith
-
ExecutionCentralAuth cookies attached to request
-
ImpactAttacker captures session tokens
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the Wikipedia Android App's SharedPreferenceCookieManager to attach stored CentralAuth session cookies to a request destined for an attacker-controlled domain. The specific prerequisite is the flawed authority matching: the pre-fix code used |
| Impact | The vendor-supplied CVSS is 4.0-only (5.3, medium) with vector AV:N/AC:L/AT:N/PR:N/UI:P/VC:L - network reachable, low complexity, no privileges, but passive user interaction required and only limited confidentiality impact. There is no EPSS score, no CISA KEV listing, and no public exploit code, so this is not an urgent-priority item - it reads as a defense-in-depth cookie-scoping hardening fix rather than an actively exploited flaw. The signals are internally consistent: a medium CVSS driven down by UI:P and VC:L, with no exploitation-maturity evidence. One nuance the raw score understates: the leaked data is CentralAuth session/auth cookies, whose disclosure could enable account takeover, so real-world impact if exploited could exceed the 'VC:L' label - but this is gated behind the attacker persuading the app to contact a lookalike domain, which materially limits practicality. No SSVC decision data was provided in the input. Overall: low-to-medium real-world priority. |
| Exploit ScenarioDerived | An attacker registers a lookalike domain whose name ends with an approved Wikimedia authority string (the pre-fix code used a loose |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 25, 2026
The Wikipedia Android App's cookie manager could release Wikimedia CentralAuth session cookies to an attacker-controlled domain, exposing logged-in users' session tokens to interception and reuse. The flaw sits in the app's SharedPreferenceCookieManager, which matched cookie domains with a loose suffix check (domain.endsWith(domainSpec)) and did not require both the request domain and the cookie's stored domain to be genuine Wikimedia authorities, so a lookalike host such as a domain ending in wikipedia.org could match an approved suffix. Exploitation is not zero-click: it requires the target to be authenticated (holding CentralAuth cookies) and to be induced into making the app request the attacker's domain, which is why the vendor scores it 5.3 (medium) and our independent assessment lands at CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N; no public exploit code or confirmed in-the-wild exploitation was identified at time of analysis, and the underlying logic is fixed by upstream pull request 6768.
RemediationAI
The upstream fix is available (PR/commit); a released patched version is not independently confirmed from the provided data - pull request 6768 (https://github.com/wikimedia/apps-android-wikipedia/pull/6768, tracked as https://phabricator.wikimedia.org/T433832) changes SharedPreferenceCookieManager.kt so cookie domains are matched exactly or as a dot-delimited subdomain (domain == domainSpec || domain.endsWith(".$domainSpec")) and so cross-authority CentralAuth transfer only occurs when the request domain itself passes Service.isWikimediaAuthority(). Until a patched build is available on the channel in use, apply compensating controls with explicit trade-offs: instruct users to avoid following untrusted or shortened links that might open URLs inside the app, since the attack requires the app to issue a request to the attacker's domain (this reduces but does not eliminate exposure, and it depends entirely on user behaviour); clear the app's stored cookies through Android's app-data settings or log out of the app to invalidate the CentralAuth values that would be leaked (this forces re-authentication on all Wikimedia properties and loses local session state); and where an organization manages the app via MDM, restrict or block usage until the fixed build is distributed. Server-side revocation of exposed CentralAuth sessions is the only reliable follow-up once a leak is suspected, because a captured token remains usable until invalidated.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is org.wikipedia.dataclient.SharedPreferenceCookieManager, a Kotlin class in the Wikipedia Android app that persists OkHttp Cookie objects in Android SharedPreferences and later decides, via loadForRequest, which stored cookies to attach to an outgoing API request for a given URL authority. Because the app is used across many Wikimedia properties (wikipedia.org, wikimedia.org, wikidata.org, language subdomains and their .m. mobile variants), it deliberately transfers CentralAuth cookies - the CentralAuth_Token and CentralAuth_User values used by Wikimedia's single-sign-on - between approved authorities. The pre-fix matching logic used a bare suffix test, domain.endsWith(domainSpec), so any host whose name merely ended with an approved authority string (for example wikipedia.org.example.com) satisfied the check; the second branch also allowed transfer whenever the cookie's stored domain was a Wikimedia authority without verifying that the request domain was as well. The upstream fix in PR 6768 tightens this to exact equality or a dot-delimited subdomain match (domain == domainSpec || domain.endsWith(".$domainSpec")) and additionally requires Service.isWikimediaAuthority(domain) on the request side before any cross-authority CentralAuth transfer occurs. CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) is the correct root-cause class: no memory-safety or injection primitive is involved, only an over-permissive string comparison that leaks credentials to a party that is not an authorized recipient.
Know when Wikipedia Android App gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Network-reachable, low complexity, no privileges, but requires user interaction to reach an attacker domain (UI:R); only limited cookie confidentiality exposure, no integrity/availability impact.
Primary rating from Vendor (wikimedia-foundation).
CVSS VectorVendor: wikimedia-foundation
DescriptionCVE.org
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Wikimedia Foundation Wikipedia Android App allows Accessing/Intercepting/Modifying HTTP Cookies.
This issue affects Wikipedia Android App: main.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-87344
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB