Poll MakerWordPress extension · Ays Pro

CVE-2024-9475

HIGH · 7.2 CVSS v3.1 Published 2024-10-26
Fix available
A fix is available. Upgrade to 5.4.7 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 generic SQL Injection via the order_by parameter in all versions up to, and including, 5.4.6 due to insufficient escaping on the user-supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with administrator-level permissions and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 up to version 5.4.6 contains a SQL injection vulnerability in the order_by parameter. The parameter is not properly escaped before being used in SQL queries, and the existing queries lack sufficient preparation (parameterized statements), allowing authenticated administrators to inject arbitrary SQL commands to extract sensitive database information.

MitigationUpdate the Poll Maker plugin to version 5.4.7 or later. If no update is available, consider removing the plugin until a patch is released.

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
Affected:< 5.4.7

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 checks

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

  1. Check installed Poll Maker plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Poll Maker and note the version number displayed
    Affected if Version shown is 5.4.6 or lower (below 5.4.7)
  2. Confirm plugin is active
    Verify in WordPress admin under Plugins that Poll Maker shows as Active
    Affected if Plugin is active and version is below 5.4.7
  3. Inspect HTTP requests to Poll Maker endpoints
    If you have access logging or a web application firewall, search for requests to Poll Maker admin pages containing the 'order_by' parameter. Look for requests with unusual characters like quotes, semicolons, or SQL keywords
    Affected if Requests with 'order_by' parameter contain SQL injection patterns
  4. Review database activity logs
    Check database query logs, plugin security logs, or WordPress debug logs for suspicious SQL queries originating from Poll Maker functionality
    Affected if Unexpected or arbitrary SQL queries appear in logs tied to Poll Maker

Environment is affected if the Poll Maker plugin version is below 5.4.7 and the plugin is active on the WordPress site.

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
Upgrade available Upgrade to 5.4.7 or later
Fixed in 5.4.7
Interim mitigation

Update the Poll Maker plugin to version 5.4.7 or later. If no update is available, consider removing the plugin until a patch is released.

Recommended fix High confidence

Poll Maker version 5.4.7

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Poll Maker' plugin in the list
  4. Click 'Update now' if an update is available, or manually update to version 5.4.7
  5. Verify the update completed successfully

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 / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9475 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-9475 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