Wp Poll MakerWordPress extension · Infotheme
CVE-2024-32514
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in Poll Maker & Voting Plugin Team (InfoTheme) WP Poll Maker.This issue affects WP Poll Maker: from n/a through 3.4.
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 WP Poll Maker plugin up to version 3.4 contains an unrestricted file upload vulnerability allowing attackers to upload dangerous file types (such as executable PHP scripts) directly to the server. With a CVSS 9.9 rating, this vulnerability can lead to remote code execution and complete site compromise if exploited.
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
Wp Poll MakerWordPress extension
< 3.5CVSS 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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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.
-
Identify the installed version of WP Poll MakerCheck the plugin version in WordPress under Plugins > Installed Plugins > Poll Maker, or inspect the main plugin file (usually wp-content/plugins/poll-maker-wp/ays-poll.php or similar) for the 'Version' header commentAffected if Installed version is 3.4 or lower (any version below 3.5)
-
Verify file upload capability is accessibleLog in to WordPress admin and navigate to the Poll Maker plugin settings to confirm the poll creation/upload feature is present and enabledAffected if The plugin's poll creation interface with file/image upload option is accessible to users (especially unauthenticated or low-privileged users)
-
Inspect the upload directory configurationCheck the plugin's source code for the upload directory path (commonly wp-content/uploads/ays-poll/) and verify file type validation is absent or weak in the upload handler codeAffected if The upload handler lacks proper file type validation or allows executable extensions like .php, .phtml, .phar
-
Scan for suspicious files in upload directoriesUse FTP, SSH, or file manager to list files in wp-content/uploads/ and subdirectories, looking for recently added PHP files or other executables with unusual namesAffected if Unexpected PHP files or scripts exist in upload directories, especially if created recently or with randomized names
You are affected if the Poll Maker plugin version is 3.4 or lower AND the file upload feature is accessible to users without proper restrictions.
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 · scoped3.5
Immediately restrict file upload functionality to whitelist only safe, non-executable file types (images, documents) and implement server-side content validation; consider disabling the plugin or blocking upload endpoints until a patched version is available.
WP Poll Maker version 3.5 or later
- Create a full backup of the WordPress site including database and files
- Navigate to WordPress admin dashboard > Plugins > Installed Plugins
- Find 'WP Poll Maker' plugin and click 'Update now' to upgrade to version 3.5 or later
- Alternatively, download WP Poll Maker 3.5 from the official WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
- After update, verify the version number shows 3.5 or higher in the plugins list
- Test that poll creation and voting functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wp Poll Maker
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-32514 — 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-2024-32514 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