Wp Poll MakerWordPress extension · Infotheme
CVE-2024-31240
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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in InfoTheme WP Poll Maker.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 · moderate confidencePath traversal vulnerability in WP Poll Maker allows attackers to access files outside the restricted directory using '../' sequences in user-controlled input. This improper limitation of pathname to restricted directory enables unauthorized file system access.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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.
-
Verify WP Poll Maker is installedCheck WordPress plugins directory or wp-content/plugins folder for 'wp-poll-maker' or 'wp-poll-maker' folder; alternatively, query the wp_options table for active_plugins or the plugins list in WordPress adminAffected if WP Poll Maker plugin is present in the WordPress installation regardless of version status
-
Determine installed versionRead the main plugin file header (e.g., wp-poll-maker.php) for the 'Version' tag, or check the plugins list in WordPress admin dashboard under Plugins > Installed PluginsAffected if Installed version is lower than 3.4 (e.g., 3.3, 3.2, older)
-
Identify file handling featuresExamine plugin source code for functions handling file paths, file uploads, or file inclusion (e.g., functions using $_GET/$_POST parameters for file paths, include/require statements with user input)Affected if Plugin contains file handling code that accepts external input for file paths without sanitization
-
Check for path traversal indicatorsReview web server access logs and WordPress debug logs for requests containing '../' sequences targeting the poll maker endpoint (e.g., ?poll_file=../, ?file=../../)Affected if Logs show suspicious requests with '../' patterns directed at poll-related URLs
-
Audit file permissionsVerify that the wp-content/uploads directory and other sensitive paths have restrictive permissions (e.g., 755 for directories, 644 for files) and are not writable by the web server processAffected if File permissions allow the web server user to write or modify files outside intended upload directories
You are affected if WP Poll Maker version is below 3.4 AND the plugin has file handling functionality that processes user-supplied path parameters.
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 to the latest version of WP Poll Maker when available. Until then, restrict file access permissions and monitor for suspicious patterns using '../' in requests.
WP Poll Maker version 3.4 or later
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate WP Poll Maker in the plugin list
- Check the current version number to confirm it is below 3.4
- Click on 'Update now' if an update to version 3.4 or later is available, or manually download version 3.4+ from the WordPress plugin repository
- If no automatic update is available, deactivate the current plugin, delete it, and upload/install version 3.4 or later from a trusted source
- After updating, verify the plugin is functioning correctly and test poll functionality
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wp Poll Maker
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31240 — 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-31240 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