An issue was discovered in the PushToWatch extension for MediaWiki through 1.35.1.

published 2020-12-21 5y ago modified 2026-06-17 4mo ago also BIT-mediawiki-2020-35626 , EUVD-2020-23292

cvss: 8.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 44%
public exploits: 0; none known

An issue was discovered in the PushToWatch extension for MediaWiki through 1.35.1. The primary form did not implement an anti-CSRF token and therefore was completely vulnerable to CSRF attacks against onSkinAddFooterLinks in PushToWatch.php.

Patch / fix

fixed in 1 links 1

bitnami mediawiki 1.35.2

gerrit.wikimedia.org/r/q/14dc79b1f44c2a1ca6b1192284206c7b8626fb57 advisory

Is CVE-2020-35626 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.52% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	8.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD	2.0	6.8	AV:N/AC:M/Au:N/C:P/I:P/A:P
OSV	3.1	8.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
bitnami	mediawiki	<1.35.2	1.35.2

Classification

Weakness

CWE-352 Cross-Site Request Forgery

References

gerrit.wikimedia.org /r/q/14dc79b1f44c2a1ca6b1192284206c7b8626fb57
patch, third-party-advisory, web
phabricator.wikimedia.org /T268641
third-party-advisory, web
nvd.nist.gov /vuln/detail/CVE-2020-35626
web

Sources

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.