dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-49044

HIGH · 7.1 CVSS v3.1 Published 2025-08-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in tosend.it Simple Poll simple-poll allows Stored XSS.This issue affects Simple Poll: from n/a through <= 1.1.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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the tosend.it Simple Poll plugin (versions <=1.1.1) allows remote attackers to inject malicious JavaScript code through crafted requests. Since the injected payload is stored by the application, this leads to Stored XSS that executes whenever users view the affected poll.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations and ensure proper output encoding/validation on data rendering to prevent stored XSS execution.

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 checks

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

  1. Identify the installed Simple Poll plugin version
    Locate the tosend.it Simple Poll plugin in your WordPress installation (typically in wp-content/plugins/) and check the main plugin file header for the 'Version' field, or view it via WordPress admin Plugins page
    Affected if The plugin version is 1.1.1 or lower
  2. Confirm the plugin is active
    Check if the Simple Poll plugin is enabled in your WordPress admin under Plugins > Installed Plugins
    Affected if The plugin shows as 'Active' in the plugin list
  3. Verify poll functionality is in use
    Look for any polls created with the Simple Poll plugin - check the WordPress database or the plugin's admin interface for existing polls
    Affected if One or more polls exist in the system
  4. Inspect stored poll data for injection points
    Examine the database tables where poll questions and answers are stored (typically via phpMyAdmin or WP CLI) - look for HTML/script tags in poll content fields
    Affected if Any poll contains raw HTML, script tags, or JavaScript event handlers in title/option fields

If Simple Poll version 1.1.1 or lower is active and polls exist with unencoded HTML/JavaScript in their stored data, the environment is vulnerable to stored XSS via CSRF.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations and ensure proper output encoding/validation on data rendering to prevent stored XSS execution.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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