WordPress plugin
YAWPP (Yet Another WordPress Petition Plugin) security & vulnerabilities
Unpatched vulnerability in the latest version
At least one vulnerability affects the latest version and no fix has been released. Deactivate the plugin or restrict access to the affected feature until the vendor ships a patch.
- Critical0
- High1
- Medium1
- Low0
All YAWPP (Yet Another WordPress Petition Plugin) vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium6.1 | Cross-Site Scripting ≤1.2.2No patch available | CVE-2015-9391 | |
| High8.8 | Authenticated SQL Injection ≤1.2.1Update to 1.2.2 | CVE-2014-5182 |
- Medium6.1Cross-Site Scripting
≤1.2.2No patch available
- High8.8Authenticated SQL Injection
≤1.2.1Update to 1.2.2
YAWPP (Yet Another WordPress Petition Plugin): common questions
Does YAWPP (Yet Another WordPress Petition Plugin) have known vulnerabilities?
Yes. VulnCrest Radar lists 2 known vulnerabilities in YAWPP (Yet Another WordPress Petition Plugin): 1 high, 1 medium. At least one is not fixed in the latest version.
How do I check which version of YAWPP (Yet Another WordPress Petition Plugin) I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent YAWPP (Yet Another WordPress Petition Plugin) vulnerability?
CVE-2015-9391, published Dec 9, 2015: YAWPP (Yet Another WordPress Petition Plugin) <= 1.2.2 - Cross-Site Scripting. Severity: Medium (CVSS 6.1).
Is any YAWPP (Yet Another WordPress Petition Plugin) vulnerability listed in CISA KEV?
No. None of the known YAWPP (Yet Another WordPress Petition Plugin) vulnerabilities is currently listed in the CISA KEV catalog.