dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-12575

MEDIUM · 5.3 CVSS v3.1 Published 2025-08-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The Poll Maker – Versus Polls, Anonymous Polls, Image Polls plugin for WordPress is vulnerable to Basic Information Exposure in all versions up to, and including, 5.8.9 via the 'ays_finish_poll' AJAX action. This makes it possible for unauthenticated attackers to retrieve admin email information which is exposed in the poll response.

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 · high confidence

The Poll Maker WordPress plugin has an information disclosure vulnerability in the 'ays_finish_poll' AJAX action. This endpoint is accessible to unauthenticated users and exposes admin email addresses that are embedded in poll response data, allowing any visitor to harvest admin contact information without authentication.

MitigationUpdate the plugin to version 5.8.10 or later once available. Until then, restrict access to the ays_finish_poll AJAX action or add capability checks to prevent unauthenticated access to sensitive poll metadata.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Poll Maker plugin version
    In the WordPress admin, go to Plugins > Installed Plugins and locate Poll Maker. The version number is displayed below the plugin name. Alternatively, check the version in the plugin's main PHP file header or in the readme.txt file within the plugin directory.
    Affected if The installed version is lower than 5.8.10
  2. Verify the ays_finish_poll AJAX endpoint is publicly accessible
    Send a POST request to /wp-admin/admin-ajax.php with action=ays_finish_poll without providing authentication credentials (no cookies or valid nonce). Use a tool like curl: curl -X POST https://your-site.com/wp-admin/admin-ajax.php -d 'action=ays_finish_poll'
    Affected if The endpoint returns a valid HTTP 200 response instead of requiring authentication
  3. Check if poll response data exposes admin email addresses
    Submit a request to the ays_finish_poll endpoint with a valid poll_id parameter (for example: curl -X POST https://your-site.com/wp-admin/admin-ajax.php -d 'action=ays_finish_poll&poll_id=1'). Examine the JSON response for any email address fields, particularly in metadata or configuration data.
    Affected if The response contains email addresses, especially those appearing to be administrator contact addresses embedded in poll configuration or metadata

You are affected if the Poll Maker plugin version is below 5.8.10 AND the ays_finish_poll AJAX endpoint is accessible without authentication and returns admin email addresses in its response.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 5.8.10 or later once available. Until then, restrict access to the ays_finish_poll AJAX action or add capability checks to prevent unauthenticated access to sensitive poll metadata.

Recommended fix Moderate confidence

Latest version available on WordPress plugin repository (version after 5.8.9)

  1. 1. Log in to the WordPress admin dashboard.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate the 'Poll Maker – Versus Polls, Anonymous Polls, Image Polls' plugin.
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. Alternatively, download the latest version from the WordPress plugin repository (plugins.trac.wordpress.org) and upload it manually.
  6. 6. After updating, verify the plugin is functioning correctly by creating a test poll.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12575 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-12575 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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