CVE-2015-8001 json
The chunked upload API (ApiUpload) in MediaWiki before 1.23.11, 1.24.x before 1.24.4, and 1.25.x before 1.25.3 does not restrict the upload…
published 11y ago modified 4mo ago also EUVD-2015-7897
- cvss
- 3.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
The chunked upload API (ApiUpload) in MediaWiki before 1.23.11, 1.24.x before 1.24.4, and 1.25.x before 1.25.3 does not restrict the uploaded data to the claimed file size, which allows remote authenticated users to cause a denial of service via a chunk that exceeds the file size.
Patch / fix
- mediawiki Debian 14, Debian 13, Debian 12 1:1.25.5-1
debian advisories DEBIAN-CVE-2015-8001
Is CVE-2015-8001 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2015-8001 updated cvss 5.8
mediawiki: multiple flaws fixed in 1.25.3, 1.24.4, and 1.23.11
-
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.57% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-284 Improper Access Control
References
-
lists.wikimedia.org
/pipermail/mediawiki-announce/2015-October/000181.html
mailing-list, patch, vendor-advisory
-
phabricator.wikimedia.org
/T91203
vendor-advisory
-
securitytracker.com
/id/1034028
vdb-entry
Sources
- CVE List CVE-2015-8001
- NVD CVE-2015-8001
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.