CVE-2020-29004

HIGHNVD 8.88.8—

8.8

The API in the Push extension for MediaWiki through 1.35 did not require an edit token in ApiPushBase.php and therefore facilitated a CSRF attack.

CVSS v3: 8.8
EG Score: 8.8(medium)
EPSS: 36.2%
KEV: Not listed

Published

January 29, 2021

Last Modified

November 21, 2024

References (6)

cve@mitrehttps://gerrit.wikimedia.org/r/c/mediawiki/extensions/Push/+/625988
cve@mitrehttps://gerrit.wikimedia.org/r/c/mediawiki/extensions/Push/+/625988/10/src/api/ApiPushBase.php
cve@mitrehttps://phabricator.wikimedia.org/T262724
af854a3a-2127-422b-91ae-364da2661108https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Push/+/625988
af854a3a-2127-422b-91ae-364da2661108https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Push/+/625988/10/src/api/ApiPushBase.php
af854a3a-2127-422b-91ae-364da2661108https://phabricator.wikimedia.org/T262724

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-352Cross-Site Request Forgery (CSRF)

Data Freshness Timeline

(refreshed 13× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-06 13:46 UTCepss_batch
2026-06-06 13:45 UTCepss_batch
2026-06-05 22:45 UTCepss_batch
2026-06-05 22:45 UTCepss_batch
2026-06-05 06:08 UTCepss_batch
2026-06-05 06:08 UTCepss_batch
2026-06-04 13:10 UTCepss_batch
2026-06-04 13:10 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-27 13:39 UTCepss_batch

Frequently asked(5)

What is CVE-2020-29004?

CVE-2020-29004 is a high vulnerability published on January 29, 2021. The API in the Push extension for MediaWiki through 1.35 did not require an edit token in ApiPushBase.php and therefore facilitated a CSRF attack.

When was CVE-2020-29004 disclosed?

CVE-2020-29004 was first published in the National Vulnerability Database on January 29, 2021, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2020-29004 actively exploited?

CVE-2020-29004 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 36.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2020-29004?

CVE-2020-29004 has a CVSS v3 base score of 8.8 (NVD).

How do I remediate CVE-2020-29004?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-29004, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-29004

Explore →

Is Your Infrastructure Affected by CVE-2020-29004?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2020-29004

📅 Published

🔄 Last Modified

🔗 References (6)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2020-29004?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (6)

Frequently asked(5)

Related CVEs(same CWE)