CVE-2023-27449
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 · uneditedMissing Authorization vulnerability in TotalSuite Total Poll Lite allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Total Poll Lite: from n/a through 4.8.6.
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 confidenceThis is a missing authorization vulnerability in Total Poll Lite WordPress plugin that allows unauthenticated or unauthorized users to bypass access controls due to incorrectly configured security levels. The flaw enables attackers to access functionality or data that should be restricted based on privilege levels.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 Total Poll Lite plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Total Poll Lite' or 'Total Poll' in the plugin listAffected if Total Poll Lite plugin is present on the WordPress site
-
Identify installed plugin versionIn the plugins list, click on 'View details' next to Total Poll Lite to display the version number, or check the plugin header in wp-content/plugins/totalpoll/plugin.php for the 'Version' tagAffected if The installed version matches or falls within the affected version range for CVE-2023-27449
-
Review WordPress user roles and capabilitiesUse a role manager plugin or query wp_options table for 'wp_user_roles' to enumerate defined roles, then check if poll creation or editing capabilities are improperly assigned to low-privilege rolesAffected if Roles such as Subscriber or Contributor have permissions to create, edit, or delete polls that should be restricted to Administrator or Editor roles
-
Inspect poll access controlsAttempt to access poll management URLs (such as /wp-admin/admin.php?page=totapoll_polls) using a browser while logged in as a subscriber-level user, or inspect AJAX actions in the browser console for poll operationsAffected if Unauthenticated requests or low-privilege users can successfully create, modify, view, or delete polls without proper authorization checks
A site is affected if Total Poll Lite is installed and either the version is within the vulnerable range or unauthorized users can access poll management functionality that should require higher privileges.
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 proper authorization checks for all sensitive operations and ensure access control security levels are correctly configured according to the principle of least privilege. Verify all user roles have appropriate permission validation before executing privileged actions.
- 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-2023-27449 — 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-2023-27449 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