Poll MakerWordPress extension · Ays Pro
CVE-2024-56295
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 · uneditedMissing Authorization vulnerability in Ays Pro Poll Maker poll-maker allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Poll Maker: from n/a through <= 5.5.6.
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 confidenceMissing authorization in the Ays Pro Poll Maker WordPress plugin allows authenticated users to access functionality beyond their intended permission level due to incorrectly configured access control security levels. The vulnerability stems from insufficient capability checks on certain poll management operations, potentially allowing lower-privileged users to modify or view polls they should not have access to.
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.5.7CVSS 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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
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.
-
Confirm Poll Maker plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Poll Maker' or 'Ays Pro Poll Maker' in the list. Note whether it is active or inactive.Affected if The plugin is installed and active.
-
Identify installed version numberIn the Plugins list, click on the plugin name or view the plugin files. The version number is displayed on the plugin page under the plugin name, or in the plugin's main PHP file header (look for 'Version:' tag).Affected if The version is less than 5.5.7 (e.g., 5.5.6, 5.5.5, etc.).
-
Verify WordPress user roles presentGo to Users > All Users in WordPress admin. Note the roles assigned to non-administrator users (e.g., Editor, Author, Contributor, Subscriber).Affected if Non-administrator user accounts exist with access to the WordPress admin area.
-
Check for poll management accessLog in as a lower-privileged user (e.g., Editor or Author) and attempt to access the Poll Maker plugin menu. Try creating, editing, or deleting polls. Observe whether these actions are allowed without proper permission checks.Affected if Lower-privileged users can create, modify, or delete polls that they should not have access to based on their role permissions.
If Poll Maker plugin is active at version 5.5.6 or lower, and lower-privileged authenticated users can access poll management functions they should not be able to, the environment is affected by this CVE.
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.5.7
Update Poll Maker plugin to the latest version which should include proper capability checks and authorization controls. If no update is available, implement WordPress capability checks (e.g., current_user_can()) on all poll-related admin and AJAX actions.
5.5.7
- Backup your WordPress database and files before making any changes
- Navigate to WordPress admin dashboard > Plugins
- Locate 'Poll Maker' plugin in the installed plugins list
- Click 'Update now' if an update is available, or manually upload version 5.5.7 from the WordPress repository
- After updating, verify the plugin version shows 5.5.7 or higher in the plugins list
- Test that poll creation, voting, and administrative functions work correctly
- Review user role permissions to ensure access controls are properly enforced
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
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-56295 — 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-56295 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