Poll MakerWordPress extension · Ays Pro
CVE-2024-3601
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 Poll Maker – Best WordPress Poll Plugin plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the ays_poll_create_author function in all versions up to, and including, 5.1.8. This makes it possible for unauthenticated attackers to extract email addresses by enumerating them one character at a time.
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 Poll Maker WordPress plugin has a broken access control vulnerability due to a missing capability check on the ays_poll_create_author function. This allows unauthenticated attackers to enumerate and extract email addresses from the WordPress database by making repeated requests to guess characters one at a time.
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
Poll MakerWordPress extension
< 5.1.9CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 Poll Maker plugin is installedCheck your WordPress site's installed plugins list for 'Poll Maker' or 'Ays Pro Poll Maker' and note the installed version numberAffected if The plugin is installed and the version is below 5.1.9
-
Confirm the vulnerable function is presentInspect the plugin files for the function 'ays_poll_create_author' - this is typically located in the main plugin PHP file under includes/classesAffected if The function exists without a capability check (missing current_user_can() or similar authorization) before it executes
-
Test unauthenticated endpoint accessSend a crafted request to the poll creation endpoint that would trigger ays_poll_create_author without providing authentication credentialsAffected if The endpoint responds without requiring login (HTTP 200 instead of redirecting to login or returning 403) - this indicates the broken access control is exploitable
-
Review access logs for exploitation signsSearch web server access logs for repeated POST requests to poll-related AJAX endpoints with incremental patterns in parameters (common in blind character guessing attacks)Affected if You see unusual numbers of requests with sequential patterns targeting poll endpoints from unauthenticated IP addresses
Your environment is affected if Poll Maker plugin version is below 5.1.9 AND the vulnerable ays_poll_create_author function is exposed without authentication, allowing potential email enumeration attacks.
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.
dbcve · scoped5.1.9
Update the Poll Maker plugin to version 5.1.9 or later which includes proper authorization checks. Until updated, consider restricting access to the vulnerable endpoint via web application firewall rules.
Poll Maker plugin version 5.1.9
- Backup your WordPress site database and files before making any changes
- Navigate to WordPress admin dashboard > Plugins section
- Locate 'Poll Maker' plugin in the installed plugins list
- Click 'Update now' when version 5.1.9 is available, or manually upload version 5.1.9 if automatic update is not showing
- Verify the plugin version shows 5.1.9 after update completion
- Test that poll creation functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Poll Maker
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-2024-3601 — 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-3601 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