dbcve.org
Poll MakerWordPress extension · Ays Pro

CVE-2023-50904

MEDIUM · 5.3 CVSS v3.1 Published 2024-12-09
Fix available
A fix is available. Upgrade to 4.8.1 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
Missing 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 <= 4.8.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 confidence

A missing authorization vulnerability in the Poll Maker WordPress plugin (versions <= 4.8.0) allows attackers to exploit incorrectly configured access control security levels. The plugin fails to properly validate user permissions before allowing access to certain functionality, potentially enabling unauthorized users to access or manipulate poll data they should not have permission to access.

MitigationImplement proper authorization checks (capability checks and nonce verification) on all sensitive functions and AJAX actions within the plugin, ensuring that users can only access poll data and operations appropriate to their role-based permissions.

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:< 4.8.1

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

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

  1. Verify Poll Maker plugin is installed
    Navigate to WordPress admin dashboard > Plugins and confirm 'Poll Maker' or 'Ays Pro Poll Maker' appears in the installed plugins list. Alternatively, check if the directory 'wp-content/plugins/poll-maker' exists on the server.
    Affected if The plugin is installed and active on the WordPress site.
  2. Determine installed plugin version
    In WordPress admin > Plugins > Installed Plugins, find Poll Maker and read the version number from the plugin description. Alternatively, inspect the plugin's main PHP file or readme.txt for the 'Version' header.
    Affected if The installed version is lower than 4.8.1 (e.g., 4.8.0 or earlier).
  3. Identify exposed AJAX actions
    Inspect the plugin's main PHP file (typically poll-maker.php) and look for AJAX action hooks registered with 'wp_ajax_' or 'wp_ajax_nopriv_' prefixes. Common vulnerable patterns include actions like 'poll-maker_save_poll', 'poll-maker_delete_poll', or similar poll manipulation functions.
    Affected if AJAX actions related to poll creation, editing, or deletion are registered without capability checks (e.g., missing 'current_user_can()' calls or nonce verification).
  4. Test unauthorized access to poll functions
    Using a low-privilege user account (subscriber level or no role), attempt to access the plugin's admin functions directly via URL or intercept AJAX requests. Common vulnerable endpoints follow patterns like '/wp-admin/admin-ajax.php?action=poll-maker_admin_action'.
    Affected if A user without administrator privileges can access or modify poll data that should require higher-level permissions.

If the Poll Maker plugin is installed with a version below 4.8.1 and exposes AJAX actions or admin functions without proper capability checks, the site is affected by this authorization bypass vulnerability.

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 4.8.1 or later
Fixed in 4.8.1
Interim mitigation

Implement proper authorization checks (capability checks and nonce verification) on all sensitive functions and AJAX actions within the plugin, ensuring that users can only access poll data and operations appropriate to their role-based permissions.

Recommended fix Moderate confidence

Poll Maker version 4.8.1

  1. 1. Backup your WordPress site and database before performing any updates.
  2. 2. Log in to your WordPress admin dashboard.
  3. 3. Navigate to Plugins > Installed Plugins.
  4. 4. Find 'Poll Maker' in the plugin list.
  5. 5. If an update is available, click 'Update Now' to upgrade to version 4.8.1 or later.
  6. 6. Alternatively, download version 4.8.1 from the WordPress Plugin Repository or the vendor's official source.
  7. 7. Deactivate the current Poll Maker plugin, then delete it, and install the new version.
  8. 8. After upgrade, verify the plugin is functioning correctly and test that authorization controls are working as expected.

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
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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