CVE-2016-6335 json
MediaWiki before 1.23.15, 1.26.x before 1.26.4, and 1.27.x before 1.27.1 does not generate head items in the context of a given title, whic…
published 2017-04-20 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-7262
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
MediaWiki before 1.23.15, 1.26.x before 1.26.4, and 1.27.x before 1.27.1 does not generate head items in the context of a given title, which allows remote attackers to obtain sensitive information via a parse action to api.php.
Patch / fix
- mediawiki Debian 14, Debian 13, Debian 12 1:1.27.1-1
debian advisories DEBIAN-CVE-2016-6335
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2016-6335 updated
mediawiki: multiple flaws fixed in 1.27.1, 1.26.4 and 1.23.15
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.68% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
phabricator.wikimedia.org
/T139570
patch, third-party-advisory
-
lists.wikimedia.org
/pipermail/mediawiki-announce/2016-August/000195.html
mailing-list, patch, vendor-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=1369613
issue-tracking
-
phabricator.wikimedia.org
/T139565
third-party-advisory
Sources
- CVE List CVE-2016-6335
- NVD CVE-2016-6335
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.