Poll MakerWordPress extension · Ays Pro

CVE-2024-56277

MEDIUM · 5.3 CVSS v3.1 Published 2025-01-21
Fix available
A fix is available. Upgrade to 5.5.5 or later.
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
Improper Encoding or Escaping of Output vulnerability in Ays Pro Poll Maker poll-maker.This issue affects Poll Maker: from n/a through < 5.5.5.

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 confidence

This is a Cross-Site Scripting (XSS) vulnerability in the Poll Maker WordPress plugin where user-supplied input is not properly encoded or escaped before being rendered in output. Attackers can inject malicious scripts that execute in the context of other users' browsers, potentially leading to session hijacking or credential theft.

MitigationUpgrade to Poll Maker version 5.5.5 or later, which includes proper output encoding. Until patched, limit administrative access and consider disabling the plugin if possible.

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.5.5

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Locate the Poll Maker plugin version
    In WordPress admin dashboard, go to Plugins > Installed Plugins > Ays Pro Poll Maker and read the version number displayed under the plugin name. Alternatively, check the plugin's main PHP file header or readme.txt for the Version field.
    Affected if The installed version is lower than 5.5.5 (for example, 5.5.4, 5.5.0, etc.)
  2. Confirm the plugin is active
    In WordPress admin, navigate to Plugins > Installed Plugins and verify that Ays Pro Poll Maker shows as 'Active' rather than 'Inactive'.
    Affected if The plugin is active and the version is below 5.5.5
  3. Identify if polls are publicly accessible
    Visit the website frontend and check if any poll created with Poll Maker is displayed on pages, posts, or widgets. Also check the plugin's 'All Polls' list in the admin panel to see if any polls exist.
    Affected if The plugin is active with a vulnerable version AND at least one poll is published and visible on the site (the XSS triggers when user-submitted poll responses are rendered without encoding)

You are affected if the installed Poll Maker plugin version is below 5.5.5, the plugin is active, and polls are created and displayed on the site, allowing unsanitized user input to be rendered in poll results or responses.

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.5.5 or later
Fixed in 5.5.5
Interim mitigation

Upgrade to Poll Maker version 5.5.5 or later, which includes proper output encoding. Until patched, limit administrative access and consider disabling the plugin if possible.

Recommended fix High confidence

Poll Maker version 5.5.5

  1. Backup your WordPress site database and files before making any changes
  2. Navigate to WordPress admin dashboard > Plugins
  3. Locate the Poll Maker plugin by Ays Pro
  4. Click 'Update now' to update to version 5.5.5 or later
  5. Verify the plugin version after update to confirm 5.5.5 is installed
  6. Test poll creation and rendering to verify the plugin functions 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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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