CVE-2015-9391: The yawpp plugin through 1.2.2 for WordPress has XSS via the field1 parameter.
CVE-2015-9391 is a medium-severity flaw (CVSS 6.1) affecting yawpp. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The yawpp plugin through 1.2.2 for WordPress has XSS via the field1 parameter.
Why this priority
- No elevated risk signals yet
A fixed release or distro patch exists.
Risk facts
| CVSS score | 6.1 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 1.3% (top 29%) |
| CISA exploited list | No |
| Weakness | CWE-79 |
| Published | 2019-09-20 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2015-9391?
yawpp: upgrade to newer than 1.2.2. Exact commands for each OS are on this page.
Is CVE-2015-9391 being exploited?
CVE-2015-9391 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2015-9391 affect?
CVE-2015-9391 affects yawpp. Severity is medium (CVSS 6.1). The yawpp plugin through 1.2.2 for WordPress has XSS via the field1 parameter.
How urgent is CVE-2015-9391?
Priority 39/100. No elevated risk signals yet.