CVE-2019-9914 json
The yop-poll plugin before 6.0.3 for WordPress has wp-admin/admin.php?page=yop-polls&action=view-votes poll_id XSS.
published 7y ago modified 4mo ago also EUVD-2019-19269
- cvss
- 6.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
The yop-poll plugin before 6.0.3 for WordPress has wp-admin/admin.php?page=yop-polls&action=view-votes poll_id XSS.
Patch / fix
- yop-poll yop-poll 6.0.3
Is CVE-2019-9914 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 FencerExploit prediction
1.66% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- lists.openwall.net https://lists.openwall.net/full-disclosure/2019/02/05/15 referenced PoC, tagged "exploit" by a source, unverified
- security-consulting.icu https://security-consulting.icu/blog/2019/02/wordpress-yop-poll-xss/ referenced PoC, tagged "exploit" by a source, unverified
- seclists.org http://seclists.org/fulldisclosure/2019/Mar/43 referenced PoC, tagged "exploit" by a source, unverified
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
References
-
lists.openwall.net
/full-disclosure/2019/02/05/15
exploit, mailing-list, third-party-advisory
-
security-consulting.icu
/blog/2019/02/wordpress-yop-poll-xss/
exploit, third-party-advisory
-
seclists.org
/fulldisclosure/2019/Mar/43
mailing-list, exploit, third-party-advisory
Sources
- CVE List CVE-2019-9914
- NVD CVE-2019-9914
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.