dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-39651

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
Missing Authorization vulnerability in TotalSuite Total Poll Lite totalpoll-lite allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Total Poll Lite: from n/a through <= 4.12.0.

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

Missing Authorization vulnerability in TotalSuite Total Poll Lite plugin allows attackers to bypass access control restrictions due to incorrectly configured security levels. The plugin fails to properly validate user permissions before granting access to sensitive poll functionality or data, enabling unauthorized actions.

MitigationImplement proper authorization checks at all endpoints and functions that handle sensitive poll data or administrative actions. Upgrade to a version that includes corrected access control logic.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 Total Poll Lite installation and version
    In WordPress admin dashboard, go to Plugins > Installed Plugins and locate Total Poll Lite. Note the version number displayed, or check the plugin header in /wp-content/plugins/total-poll-lite/ directory by reading the main plugin file.
    Affected if Version listed is 4.12.0 or lower (including any 4.x.x version below 4.12.0)
  2. Verify vulnerable authorization endpoint exists
    Check the plugin directory for files handling admin actions or public-facing poll submission. Look for PHP files that process poll votes or poll management requests without capability checks. Common paths include /total-poll-lite/ and subdirectories like /includes/ or /classes/.
    Affected if Files exist that process requests without checking current_user capability or nonce verification before performing sensitive operations
  3. Inspect access control configuration
    Access WordPress wp_options table or plugin settings page to examine any stored configuration related to poll access permissions, user role restrictions, or security level settings. Look for options like 'poll_visibility', 'access_control', or similar authorization-related settings.
    Affected if Configuration shows no capability checks or allows unrestricted access to poll creation/voting for unauthenticated users
  4. Test for unauthorized poll access
    Use a browser or curl to access poll management URLs (such as /wp-admin/admin.php?page=totapoll or direct AJAX endpoints) while logged out or as a low-privilege user. Observe if actions like viewing results, creating polls, or modifying settings are accessible without proper WordPress capability checks.
    Affected if Sensitive poll management functions or data are accessible without authentication or without the 'manage_options' capability
  5. Review plugin code for authorization hooks
    Examine the main plugin PHP files for presence of current_user_can() checks before sensitive operations. Search for add_action or add_filter calls that process form submissions, poll submissions, or admin actions. Compare against WordPress best practices for nonce verification and capability checks.
    Affected if No current_user_can() or similar authorization checks are found before critical operations, or checks are commented out/missing on certain functions

You are affected if Total Poll Lite version 4.12.0 or lower is installed AND certain poll management functions are accessible without proper WordPress capability verification or authentication.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks at all endpoints and functions that handle sensitive poll data or administrative actions. Upgrade to a version that includes corrected access control logic.

Recommended fix Moderate confidence

Total Poll Lite 4.12.1 or later (latest stable release)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find Total Poll Lite in the plugin list
  4. 4. Check if an update is available for the plugin
  5. 5. If an update is available, update to the latest version which should contain the authorization fix
  6. 6. Verify the update was successful and test poll functionality
Caveat Review plugin settings after upgrade as minor configuration changes may occur in feature updates

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

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