Polls CpWordPress extension · Codepeople
CVE-2014-10395
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe cp-polls plugin before 1.0.1 for WordPress has XSS in the votes list.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe cp-polls WordPress plugin before version 1.0.1 contains a stored Cross-Site Scripting (XSS) vulnerability in the votes list functionality. Attackers can inject malicious JavaScript through poll vote submissions that execute when administrators view the votes list in the WordPress admin dashboard.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Polls CpWordPress extension
< 1.0.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify cp-polls plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Codepeople Polls' or 'Cp' in the plugin list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'cp-polls' or similar.Affected if The plugin is installed and active
-
Check installed plugin versionIn WordPress admin, click on the plugin name in the plugin list to view details, or inspect the main plugin PHP file header for a 'Version' comment. Compare the version number to 1.0.1.Affected if Version is less than 1.0.1 or the version cannot be determined (older installation)
-
Confirm polls exist and voting is enabledCheck if any polls have been created by visiting the Cp Polls settings page or viewing the frontend where polls are displayed. Look for active poll forms that accept user submissions.Affected if At least one poll exists and accepts user votes
-
Verify admin panel access existsDetermine if the WordPress admin dashboard is accessible. The XSS payload executes when administrators view the votes list in the admin panel.Affected if Admin dashboard is accessible to users who can view poll results
You are affected if the Codepeople Polls Cp plugin is installed with a version lower than 1.0.1 and users can submit votes to any poll that you (or other admins) will view in the admin panel.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.0.1
Update the cp-polls plugin to version 1.0.1 or later to remediate the XSS vulnerability. If immediate update is not possible, restrict access to the WordPress admin panel to trusted users only.
Fix this in Polls Cp
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-10395 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-10395 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data