The ultimate-category-excluder plugin before 1.2 for WordPress allows ultimate-category-excluder.php CSRF.

published 2020-12-11 5y ago modified 2026-06-17 4mo ago also EUVD-2020-22827

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

Patch / fix

fixed in 1 links 1

infolific ultimate_category_excluder 1.2

plugins.trac.wordpress.org/changeset/2434070 advisory

Is CVE-2020-35135 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 Fencer

Exploit prediction

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

Exploits and checks

advisory.checkmarx.net https://advisory.checkmarx.net/advisory/CX-2020-4294 referenced PoC, tagged "exploit" by a source, unverified

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

Classification

Weakness

CWE-352 Cross-Site Request Forgery

Technology feeds

WordPress rss critical rss

References

plugins.trac.wordpress.org /changeset/2434070
patch, vendor-advisory
advisory.checkmarx.net /advisory/CX-2020-4294
exploit, third-party-advisory
wordpress.org /plugins/ultimate-category-excluder/#developers
release-notes, vendor-advisory

Sources

CVE List CVE-2020-35135
NVD CVE-2020-35135

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.