CVE-2026-27044
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 Control of Generation of Code ('Code Injection') vulnerability in TotalSuite Total Poll Lite totalpoll-lite allows Remote Code Inclusion.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 confidenceA code injection vulnerability in Total Poll Lite WordPress plugin versions up to 4.12.0 allows remote attackers to inject malicious code through improper control of code generation, potentially enabling remote code execution via included remote files.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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.
-
Confirm Total Poll Lite plugin is installedNavigate to WordPress admin > Plugins and look for 'Total Poll Lite' in the installed plugins list, or check the /wp-content/plugins/ directory for the total-poll-lite folderAffected if Plugin is not present on the WordPress installation
-
Identify the installed version of Total Poll LiteIn WordPress admin, go to Plugins > Installed Plugins > Total Poll Lite and read the version number displayed beneath the plugin name; alternatively, check the main plugin PHP file for the 'Version' header commentAffected if Version number is 4.12.0 or lower
-
Verify the feature that enables the vulnerabilityCheck if the poll functionality allows including external files or remote content sources. Review Total Poll Lite settings under Poll > Settings > Advanced for options like 'Include external file', 'Remote source', or similar file inclusion featuresAffected if File inclusion or remote content import features are enabled and accessible to users
-
Confirm the code generation mechanism is exposedInspect the plugin's ajax.php or similar endpoints that handle poll creation/saving. Look for code paths that accept user input and pass it to eval(), include(), or similar code execution functions without sanitizationAffected if User-supplied input can reach code generation or inclusion functions without proper validation
A user is affected if Total Poll Lite version 4.12.0 or lower is installed AND the plugin (or its file inclusion features) is active and accessible on the WordPress site
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 dataUpdate Total Poll Lite to the latest patched version immediately. If no patched version is available, disable the plugin until a fix is released.
- Consultation3.0 h
- Implementation8.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 $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27044 — 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-2026-27044 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