CVE-2020-29005 json
The API in the Push extension for MediaWiki through 1.35 used cleartext for ApiPush credentials, allowing for potential information disclos…
published 2021-01-29 5 y ago modified 2026-06-17 4 mo ago also BIT-mediawiki-2020-29005 , EUVD-2020-21387
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 51%
- public exploits
- 0
- none known
Summary
The API in the Push extension for MediaWiki through 1.35 used cleartext for ApiPush credentials, allowing for potential information disclosure.
Patch / fix
- bitnami mediawiki 1.35.1
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-2020-29005 updated cvss 5.3
mediawiki: Information disclosure via cleartext transmitted ApiPush credentials
-
Red Hat OpenShift Container Platform 3.11 mediawiki Red Hat OpenShift Container Platform 4 mediawikinot 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
0.66% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/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 |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | mediawiki | <1.35.1 |
1.35.1 |
Classification
References
-
phabricator.wikimedia.org
/T262724
issue-tracking, patch, vendor-advisory, web
-
gerrit.wikimedia.org
/r/c/mediawiki/extensions/Push/+/625988
patch, vendor-advisory, web
-
nvd.nist.gov
/vuln/detail/CVE-2020-29005
web
Sources
- CVE List CVE-2020-29005
- NVD CVE-2020-29005
- OSV BIT-mediawiki-2020-29005
Fencer Vulns 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.