The Custom Field Suite plugin before 2.5.15 for WordPress has XSS for editors or admins.

published 2019-05-10 7y ago modified 2026-06-17 4mo ago also EUVD-2019-3531

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

Patch / fix

fixed in 1

custom_field_suite_project custom_field_suite 2.5.15

Is CVE-2019-11871 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.93% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	5.4	CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
NVD	2.0	3.5	AV:N/AC:M/Au:S/C:N/I:P/A:N

Classification

Weakness

CWE-79 Improper Neutralization of Input During Web Page Generation

Technology feeds

WordPress rss critical rss

References

wordpress.org /plugins/custom-field-suite/#developers
product, release-notes, third-party-advisory
blog.reddy.io /2019/05/30/xss-injection-vulnerability-in-custom-field-suite-wordpress-plugin/
wpvulndb.com /vulnerabilities/9273

Sources

CVE List CVE-2019-11871
NVD CVE-2019-11871

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.