Poll MakerWordPress extension · Ays Pro
CVE-2025-26971
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 Special Elements used in an SQL Command ('SQL Injection') vulnerability in Ays Pro Poll Maker poll-maker allows Blind SQL Injection.This issue affects Poll Maker: from n/a through <= 5.6.5.
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 confidenceAys Pro Poll Maker plugin for WordPress versions up to 5.6.5 contains a blind SQL injection vulnerability. An unauthenticated attacker can inject malicious SQL queries through vulnerable parameters, potentially allowing extraction of sensitive database information, authentication bypass, or data manipulation. Blind SQLi requires inferring results through behavioral differences rather than direct output.
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
Poll MakerWordPress extension
< 5.6.6CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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.
-
Check the installed Poll Maker plugin versionNavigate to WordPress admin > Plugins > Installed Plugins > locate 'Ays Pro Poll Maker' and view the version number displayedAffected if The version shown is any version prior to 5.6.6 (e.g., 5.6.5, 5.6.4, etc.)
-
Verify the poll handling functionality is accessibleConfirm that the Poll Maker plugin is activated and that poll shortcodes or widgets are in use on the site, or that poll creation/editing is available in the admin panelAffected if The plugin is active and polls can be created, edited, or viewed by users (the SQL injection requires this functionality to be present)
-
Inspect database query handling for poll parametersReview the plugin code related to poll submission and retrieval (typically in files handling poll saving/loading). Look for database queries where user-supplied input (such as poll ID, answer selection, or poll response data) is directly concatenated into SQL statements rather than using prepared statementsAffected if User-provided poll data is passed directly into SQL queries without parameterization or sanitization routines
-
Check for web application firewall or input filteringExamine if the web application has WAF rules, plugin security extensions, or custom input validation middleware that could detect or block SQL injection attempts in poll-related request parametersAffected if No security filtering is present between user requests and the poll handling code
If the installed Ays Pro Poll Maker version is below 5.6.6 and the plugin is active with accessible poll functionality, the environment is likely affected by this blind SQL injection vulnerability.
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 data5.6.6
Upgrade Poll Maker to the latest version that includes parameterized queries or prepared statements to properly sanitize user input before using it in SQL queries. If no patch is available, disable the plugin until a fix is released.
Fix this in Poll Maker
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26971 — 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-26971 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