WordPress CP Polls 1.0.8 contains a cross-site request forgery vulnerability that allows attackers to perform unauthorized actions on behalf of authenticated users. Attackers can craft malicious HTML pages that execute unwanted poll operations when administrators visit the page while logged in.
Security readout for executives and security teams
Plain-English summary
This issue affects the CP Polls WordPress plugin version 1.0.8. A malicious site could cause an already logged-in administrator to perform unwanted poll-related actions. The impact is operational and integrity-focused, not direct server takeover based on the provided sources.
Executive priority
Treat as a moderate-priority WordPress plugin risk. It is unlikely to be a standalone breach path from the provided evidence, but it can undermine site integrity if administrators are targeted.
Technical view
CVE-2016-20067 is a CWE-352 CSRF flaw in dwbooster CP Polls 1.0.8 for WordPress. The source description says crafted HTML can trigger unauthorized poll operations through an authenticated user's browser session. No affected versions beyond 1.0.8 are identified.
Likely exposure
Exposure is likely limited to WordPress sites running dwbooster CP Polls 1.0.8. The bundle does not identify affected CPEs, later vulnerable versions, WordPress core impact, or hosted-service exposure.
Exploitation context
A public ExploitDB reference exists, but the bundle does not show CISA KEV listing or evidence of active exploitation. Successful abuse depends on an authenticated user context and cross-site request behavior described by the sources.
Researcher notes
The provided record names CP Polls 1.0.8 only and maps to CWE-352. Patch status is not included. Avoid broad claims about exploitation or other versions unless confirmed by vendor or additional primary sources.
Mitigation direction
Inventory WordPress sites for CP Polls version 1.0.8.
Check vendor or plugin maintainer guidance for a fixed release.
Disable or remove CP Polls where business need is low.
Limit administrator browsing while logged in to WordPress.
Prioritize patching or replacement on public-facing WordPress sites.
Validation and detection
Confirm whether CP Polls 1.0.8 is installed and active.
Review plugin changelogs or vendor notices for CSRF fixes.
Check administrative audit logs for unexpected poll changes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-352 · source CWE mapping
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.