Wp Poll MakerWordPress extension · Infotheme
CVE-2024-29818
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Poll Maker & Voting Plugin Team (InfoTheme) WP Poll Maker allows Stored XSS.This issue affects WP Poll Maker: from n/a through 3.1.
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 confidenceStored Cross-site Scripting (XSS) vulnerability in WP Poll Maker plugin versions up to 3.1 allows attackers to inject malicious JavaScript through poll fields that are stored in the database and executed when other users view the poll results or the web page where the poll is embedded.
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.4CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check WP Poll Maker plugin versionNavigate to WordPress admin > Plugins > Installed Plugins > locate WP Poll Maker and note the version number displayedAffected if Version is 3.1 or any version lower than 3.4 (the vulnerability affects versions up to 3.1)
-
Identify polls with custom input fieldsGo to WP Poll Maker in the WordPress admin panel and review existing polls. Check each poll for custom fields or questions that accept free-text user inputAffected if Any poll contains custom input fields where users can submit text responses
-
Inspect poll data in database for unsanitized contentAccess the WordPress database (via phpMyAdmin or command line) and query the poll maker tables for entries containing HTML tags, script elements, or event handlers (such as <script, javascript:, onload, onerror) in poll response fieldsAffected if Database contains poll data with raw script tags or HTML that should have been sanitized
-
Verify poll output encoding on frontendView a poll on the live site, right-click and inspect the page source. Search for any user-submitted poll responses and confirm they appear as encoded text (e.g., <script>) rather than raw executable HTMLAffected if User-supplied poll responses render as raw HTML/JavaScript when viewed by other users
If the installed WP Poll Maker version is below 3.4 AND any poll responses containing script tags or HTML are stored and rendered without encoding, the environment is affected by CVE-2024-29818
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.4
Update WP Poll Maker to the latest version and implement proper input sanitization and output encoding for all user-supplied poll data before rendering in HTML pages.
WP Poll Maker version 3.4
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate WP Poll Maker in the plugin list
- Click 'Update now' if an update is available, or manually upload version 3.4 from the WordPress plugin repository
- After updating, verify the plugin shows version 3.4 or higher
- Test poll creation and submission to confirm 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
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29818 — 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-29818 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