CVE-2025-46466
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in felixtz Modern Polls modern-polls allows Stored XSS.This issue affects Modern Polls: from n/a through <= 1.0.10.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Modern Polls WordPress plugin (versions <= 1.0.10) allows authenticated users to be tricked into submitting malicious requests that inject persistent malicious scripts (Stored XSS) into poll data. The lack of anti-CSRF token validation enables attackers to craft malicious poll submissions via social engineering.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Verify Modern Polls plugin is installedNavigate to WordPress Admin > Plugins and locate 'Modern Polls' in the installed plugins list, or check the /wp-content/plugins/ directory for the modern-polls folderAffected if Modern Polls plugin is present in the WordPress installation
-
Check installed version numberIn WordPress Admin > Plugins, find Modern Polls and view the version number displayed below the plugin name, or inspect the main plugin file (e.g., modern-polls.php) for the 'Version' header commentAffected if The installed version is 1.0.10 or lower
-
Inspect plugin source for nonce validationExamine the plugin's form handling PHP files (typically in the includes or admin folders) for state-changing actions like poll creation/editing. Search for the presence of 'wp_nonce_field', 'wp_verify_nonce', or 'check_admin_referer' function calls in form processing codeAffected if No anti-CSRF nonce validation is found in poll submission or poll management code paths
-
Test for CSRF vulnerability in poll formsCreate a test HTML page that attempts to submit a poll question to your site without a valid nonce token. Observe whether the request is accepted or rejected by the serverAffected if Poll submissions succeed without a valid CSRF token (request is accepted)
-
Search for suspicious stored content in pollsQuery the WordPress database: SELECT * FROM wp_posts WHERE post_type='mp_poll' OR SELECT * FROM wp_postmeta WHERE meta_value LIKE '%<script%' or similar XSS patterns. Also review all polls via Admin > Polls for unexpected script tags or event handlers in poll questions/optionsAffected if Poll data contains unescaped HTML/JavaScript that could execute in admin or frontend views
A user is affected if Modern Polls version 1.0.10 or lower is installed AND the plugin lacks anti-CSRF nonce validation in its poll submission handlers, allowing potential stored XSS injection via forged requests.
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.
From vendor dataImplement anti-CSRF nonce validation on all form submissions and state-changing actions in the plugin, combined with proper input sanitization and output encoding to prevent stored XSS execution.
- Consultation2.0 h
- Implementation6.0 h
- Testing4.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,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46466 — 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-2025-46466 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