Wp PollsWordPress extension · Wp Polls Project
CVE-2016-10936
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 wp-polls plugin before 2.73.1 for WordPress has XSS via the Poll bar option.
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 wp-polls plugin before version 2.73.1 for WordPress contains a stored Cross-Site Scripting (XSS) vulnerability in the Poll bar option. Attackers can inject malicious JavaScript into the poll bar configuration, which executes when other users view or interact with the poll.
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
Wp PollsWordPress extension
< 2.73.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 wp-polls plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP-Polls' in the list. Alternatively, check the /wp-content/plugins/ directory for the wp-polls folder.Affected if The wp-polls plugin folder exists in the WordPress installation
-
Check installed wp-polls versionIn WordPress admin, click on the plugin name to view details and find the version number. Alternatively, open wp-polls/wp-polls.php and look for the 'Version:' comment in the file header.Affected if The version number is less than 2.73.1 (for example, 2.73.0, 2.72, 2.71, etc.)
-
Identify existing poll bar configurationsIn WordPress admin, go to Polls > Manage Polls. Review each poll to see if any have custom poll bar settings configured (typically found in poll edit options under poll bars or styling).Affected if Any polls exist with custom poll bar configurations enabled
-
Inspect poll bar configuration for malicious contentAccess the WordPress database and query the wp_polls table, specifically examining fields that store poll bar settings (such as pollbar_color, pollbar_style, or similar poll bar configuration fields). Look for unusual characters, script tags, or encoded JavaScript.Affected if The poll bar configuration contains script tags, event handlers (onclick, onerror, onload), or other JavaScript code patterns (such as <script, javascript:, or event handlers like onmouseover)
You are affected if wp-polls version is below 2.73.1 AND any poll has custom poll bar configurations containing suspicious JavaScript code.
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 data2.73.1
Update wp-polls plugin to version 2.73.1 or later to remediate the XSS vulnerability. Review and sanitize any existing poll configurations for injected scripts.
Fix this in Wp Polls
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10936 — 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-2016-10936 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