dbcve.org
Polls CpWordPress extension · Codepeople

CVE-2015-9346

MEDIUM · 6.1 CVSS v3.0 Published 2019-08-27
Fix available
A fix is available. Upgrade to 1.0.5 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
The cp-polls plugin before 1.0.5 for WordPress has XSS.

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 confidence

The cp-polls WordPress plugin before version 1.0.5 contains a Cross-Site Scripting (XSS) vulnerability. This allows attackers to inject malicious scripts through the plugin's input fields, potentially compromising user sessions or performing actions on behalf of authenticated users.

MitigationUpdate the cp-polls plugin to version 1.0.5 or later. If immediate updating is not possible, consider disabling the plugin until the patch can be applied.

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
Affected:< 1.0.5

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the cp-polls plugin directory
    Check your WordPress installation under wp-content/plugins/ for a folder named 'cp-polls' or 'codepeople-polls'. If the folder exists, the plugin is installed.
    Affected if The plugin folder exists in wp-content/plugins/
  2. Find the installed plugin version
    Open the main plugin file (usually cp-polls.php or index.php inside the plugin folder) and look for a version comment or variable at the top of the file. Alternatively, check the plugin header in the main PHP file for 'Version:' field.
    Affected if The version found is lower than 1.0.5 (for example: 1.0.4, 1.0.3, 1.0.2, etc.)
  3. Verify the plugin is active
    Log in to WordPress admin and go to Plugins > Installed Plugins. Check if 'Codepeople Polls' or 'cp-polls' shows as 'Active'.
    Affected if The plugin is installed, active, and the version is below 1.0.5
  4. Check for XSS-susceptible input forms
    If the plugin is active, navigate to the polls created with this plugin in the frontend. Look for poll submission forms where user input is accepted. These are the areas where XSS could be triggered.
    Affected if The plugin is active and below version 1.0.5, and poll forms are accessible on the site

You are affected if the Codepeople Polls cp-polls plugin is installed with a version lower than 1.0.5 and the plugin is active on your WordPress site.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 1.0.5 or later
Fixed in 1.0.5
Interim mitigation

Update the cp-polls plugin to version 1.0.5 or later. If immediate updating is not possible, consider disabling the plugin until the patch can be applied.

Fix this in Polls Cp Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-9346 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-9346 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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