What this page helps you verify fast
This hub clusters tracked records for Polls CP so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
Review known vulnerability records for the WordPress plugin Polls CP (`cp-polls`), including severity, CVE references, affected versions, and patch status.
Recent tracked CVEs on this page include CVE-2025-50025, CVE-2024-47297 and CVE-2024-8851, so operators can jump from disclosure to patch validation without scanning the full feed first.
Pair this plugin vulnerability hub with practical WordPress hardening, scanner, and patch workflow guidance.
Review patch cadence, privileged access, XML-RPC exposure, backups, and monitoring controls.
Use ownership, update testing, least privilege, and removal criteria to reduce plugin risk.
Compare scanner coverage for plugin CVEs, version detection, alert noise, and remediation workflow.
Use the hub as a decision layer before opening individual records: confirm whether the issue has a CVE, whether a fixed version exists, and whether the affected range overlaps production installs.
Affected range: Versions up to 1.0.1. Fixed version: 1.0.2.
Affected range: Versions up to 1.0.74. Fixed version: 1.0.75.
Affected range: Versions before 1.0.5. Fixed version: 1.0.5.
Affected range: Versions before 1.0.1. Fixed version: 1.0.1.
Start with the highest-signal CVE records for this WordPress plugin before scanning the full vulnerability feed.
| Tracked CVE | Issue Type | Affected Versions | Fixed Version | CVSS |
|---|---|---|---|---|
|
CVE-2014-125091
Polls CP <= 1.0.1 - Authenticated SQL Injection
|
SQL Injection | Versions up to 1.0.1 | 1.0.2 | CVSS 8.8 |
|
CVE-2024-47297
CP Polls <= 1.0.74 - Reflected Cross-Site Scripting
|
Cross-Site Scripting | Versions up to 1.0.74 | 1.0.75 | CVSS 6.1 |
|
CVE-2015-9346
Polls CP < 1.0.5 - Cross-Site Scripting
|
Cross-Site Scripting | Versions before 1.0.5 | 1.0.5 | CVSS 6.1 |
|
CVE-2014-10395
Polls CP < 1.0.1 - Cross-Site Scripting
|
Cross-Site Scripting | Versions before 1.0.1 | 1.0.1 | CVSS 6.1 |
|
CVE-2024-24873
CP Polls <= 1.0.71 - Unauthenticated Poll Limit Bypass
|
Authorization Bypass | Versions up to 1.0.71 | 1.0.72 | CVSS 5.3 |
|
CVE-2024-24874
CP Polls <= 1.0.71 - Unauthenticated Content Injection
|
Vulnerability | Versions up to 1.0.71 | 1.0.72 | CVSS 5.3 |
|
CVE-2025-50025
CP Polls <= 1.0.81 - Authenticated (Administrator+) Stored Cross-Site Scripting
|
Stored Cross-Site Scripting | Versions up to 1.0.81 | 1.0.82 | CVSS 4.4 |
|
CVE-2024-8851
Polls CP <= 1.0.76 - Authenticated (Admin+) Stored Cross-Site Scripting
|
Stored Cross-Site Scripting | Versions up to 1.0.76 | 1.0.77 | CVSS 4.4 |
Polls CP <= 1.0.1 - Authenticated SQL Injection
CP Polls <= 1.0.74 - Reflected Cross-Site Scripting
Polls CP < 1.0.5 - Cross-Site Scripting
Polls CP < 1.0.1 - Cross-Site Scripting
CP Polls <= 1.0.71 - Unauthenticated Poll Limit Bypass
CP Polls <= 1.0.71 - Unauthenticated Content Injection
CP Polls <= 1.0.81 - Authenticated (Administrator+) Stored Cross-Site Scripting
Polls CP <= 1.0.76 - Authenticated (Admin+) Stored Cross-Site Scripting
This hub clusters tracked records for Polls CP so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
These recent records surface the CVE strings, patch cues, and direct report links most operators need first.
The CP Polls plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 1.0.81 due to insufficient input sanitization and output escaping. This makes...
The CP Polls plugin for WordPress is vulnerable to Reflected Cross-Site Scripting in versions up to, and including, 1.0.74 due to insufficient input sanitization and output escaping. This ma...
The Polls CP plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 1.0.76 due to insufficient input sanitization and outp...
Sorted by latest disclosure date so newly published issues surface first.
The CP Polls plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 1.0.81 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level access and above, to in...
The CP Polls plugin for WordPress is vulnerable to Reflected Cross-Site Scripting in versions up to, and including, 1.0.74 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages tha...
The Polls CP plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 1.0.76 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level...
The Polls CP plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 1.0.76 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level...
The Polls CP plugin for WordPress is vulnerable to Poll Limit Bypass in all versions up to, and including, 1.0.71. This is due to insufficient controls on on the voting system. This makes it possible for unauthenticated attackers to vote multiple times.
The Polls CP plugin for WordPress is vulnerable to content injection in all versions up to, and including, 1.0.71. This is due to insufficient validation on poll answers. This makes it possible for unauthenticated attackers to inject arbitrary content.
The cp-polls plugin before 1.0.5 for WordPress has XSS via the 'name' parameter.
The Polls CP plugin for WordPress is vulnerable to SQL Injection via the 'lu' parameter in all versions up to, and including, 1.0.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for...
The Polls CP plugin for WordPress is vulnerable to Cross-Site Scripting in versions up to 1.0.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts that execute in a victim's browser.