The Participants Database plugin before 1.7.5.10 for WordPress has XSS.

published 2017-09-04 9y ago modified 2026-06-17 4mo ago also EUVD-2017-5638

cvss: 6.1; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 2.3%; EPSS 2.3% chance of exploitation in 30 days, percentile 83%
public exploits: 1; Exploit-DB

Is CVE-2017-14126 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

Timeline

2017-09-01 First public exploit (EDB-42618)
2017-09-04 Published

Exploit prediction

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

Exploits and checks

EDB-42618 WordPress Plugin Participants Database < 1.7.5.10 - Cross-Site Scripting webapps, 2017-09-01

CVSS scores

assigned by	version	score	vector
NVD	3.0	6.1	CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD	2.0	4.3	AV:N/AC:M/Au:N/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

exploit-db.com /exploits/42618/
exploit
wordpress.org /plugins/participants-database/#developers
third-party-advisory
limbenjamin.com /articles/cve-2017-14126-participants-database-xss.html

Sources

CVE List CVE-2017-14126
NVD CVE-2017-14126

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.