Poll MakerWordPress extension · Ays Pro
CVE-2025-24577
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.0.
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 by Ays Pro versions up to 5.5.0 contains a Missing Authorization vulnerability allowing exploitation of incorrectly configured access control security levels. This critical flaw permits unauthenticated or unauthorized users to bypass proper permission checks and access administrative functions or sensitive poll data that should be restricted to privileged users.
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.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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 Poll Maker plugin versionCheck the installed version in WordPress admin under Plugins > Installed Plugins, look for 'Poll Maker' by Ays Pro, or inspect the plugin header in wp-content/plugins/poll-maker/ays-poll-maker.php for 'Version: x.x.x'Affected if The version is less than 5.5.1 (e.g., 5.5.0 or earlier)
-
Confirm plugin is activeVerify the Poll Maker plugin is currently activated in WordPress under Plugins > Installed PluginsAffected if The plugin is active and the version is below 5.5.1
-
Test AJAX endpoint accessibilityAttempt an unauthenticated request to wp-admin/admin-ajax.php?action=ays_poll_functions or other poll-maker AJAX actions using curl or a browser DevTools network requestAffected if The endpoint returns sensitive poll data or administrative responses without requiring authentication (HTTP 200 with data instead of redirecting to login)
-
Check for exposed poll dataUse a tool like curl or browser to access poll export or results endpoints without logging in, such as examining if poll results or settings are visible to unauthenticated usersAffected if Poll results, votes, or configuration data is accessible without being logged into WordPress
A user is affected if the Poll Maker plugin version is below 5.5.1 and the plugin is active, with AJAX endpoints or poll data accessible to unauthenticated users.
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.1
Update Poll Maker plugin to version 5.5.1 or later which contains proper authorization controls. Until patched, consider restricting access to wp-admin and the poll-maker AJAX endpoints via server-side configuration.
Poll Maker 5.5.1
- 1. Back up your WordPress site database and files before making any changes.
- 2. Navigate to the WordPress admin dashboard > Plugins section.
- 3. Locate the Poll Maker plugin in the installed plugins list.
- 4. If an update is available, click the 'Update Now' link next to Poll Maker, or download version 5.5.1 from the WordPress plugin repository and upload it manually.
- 5. After updating, verify the plugin status shows version 5.5.1 as active.
- 6. Test poll creation, voting, and administrative functions to ensure the plugin operates correctly after the update.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Poll Maker
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24577 — 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-2025-24577 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