Light PollWordPress extension · Dmytropopov
CVE-2024-6720
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 Light Poll WordPress plugin through 1.0.0 does not have CSRF checks in some places, which could allow attackers to make logged in users perform unwanted actions via CSRF attacks
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 · moderate confidenceThe Light Poll WordPress plugin through version 1.0.0 lacks CSRF token validation on certain state-changing actions. Attackers can trick logged-in administrators or users into executing unintended operations (such as modifying poll settings or data) by luring them to visit malicious pages that trigger crafted requests to the vulnerable plugin endpoints.
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
Light PollWordPress extension
<= 1.0.0CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 Light Poll plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Light Poll' by Dmytropopov. Check the version number displayed.Affected if The plugin is installed and its version is 1.0.0 or lower.
-
Locate plugin action handlersAccess the plugin files via FTP or file manager at wp-content/plugins/light-poll. Examine PHP files for functions that handle form submissions, AJAX requests, or admin operations (look for add_action hooks with 'admin_init', 'wp_ajax_', or form processing logic).Affected if The plugin contains action handlers that process state-changing requests.
-
Inspect nonce verification in action handlersOpen each identified action handler file and search for calls to wp_verify_nonce, check_ajax_referer, or wp_create_nonce. Look for the pattern 'if ( ! wp_verify_nonce(...) )' or similar validation logic near the beginning of each handler.Affected if No nonce verification is found before processing the action, or nonce checks are completely absent in the handler code.
-
Check form and AJAX calls for nonce fieldsExamine plugin PHP files that generate HTML forms or JavaScript AJAX calls. Look for wp_nonce_field, wp_nonce_url, or data: { nonce: ... } patterns in the output.Affected if Forms and AJAX calls generated by the plugin do not include nonce tokens as hidden fields or data parameters.
You are affected if the Light Poll plugin version 1.0.0 or lower is installed AND the plugin's action handlers lack CSRF token verification before processing requests.
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 dataAdd WordPress nonces to all forms and AJAX actions in the plugin, and verify the nonce on the server side before processing any state-changing request. Enforce same-origin policy compliance.
Fix this in Light Poll
Scoped from the published advisory
- Consultation3.0 h
- Implementation5.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6720 — 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-2024-6720 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