dbcve.org
InjectionWeakness · CWE-74

CVE-2026-2019

HIGH · 7.2 CVSS v3.1 Published 2026-02-18
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 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
The Cart All In One For WooCommerce plugin for WordPress is vulnerable to Code Injection in all versions up to, and including, 1.1.21. This is due to insufficient input validation on the 'Assign page' field which is passed directly to the eval() function. This makes it possible for authenticated attackers, with Administrator-level access and above, to execute arbitrary PHP code on the server.

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 confidence

The Cart All In One For WooCommerce plugin for WordPress versions up to 1.1.21 contains a code injection vulnerability in the 'Assign page' field. The field value is passed directly to PHP's eval() function without input validation or sanitization, allowing authenticated administrators to execute arbitrary PHP code on the server.

MitigationImmediately update the plugin to a version beyond 1.1.21. If no patched version exists, remove or disable the plugin until a fix is available. As an interim measure, restrict administrator role access and audit user accounts with admin privileges.

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

CVSS:3.1/AV:N/AC:L/PR:H/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 checks

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

  1. Check if Cart All In One For WooCommerce plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Cart All In One For WooCommerce' or check the wp-content/plugins directory for a folder containing 'cart-all-in-one-for-woocommerce'
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    In WordPress admin Plugins list, click on the plugin to view details and note the version number, or open the main plugin PHP file (usually cart-all-in-one-for-woocommerce.php) and look for the Version header in the plugin comments
    Affected if Version is 1.1.21 or lower
  3. Locate the Assign page setting
    Navigate to WooCommerce > Cart All In One settings or the plugin settings page and look for a field labeled 'Assign page' or similar
    Affected if The 'Assign page' field exists and is accessible in the plugin configuration
  4. Verify if the Assign page field contains a value
    In the plugin settings page, examine the 'Assign page' field - check if it contains any custom value, shortcode, or PHP code
    Affected if The field contains a non-default value (any custom entry in this field would be passed to eval())
  5. Confirm administrator access exists
    Review WordPress user roles at Users > All Users and check if any accounts have Administrator role, or check user_capabilities in wp_usermeta table
    Affected if At least one user with Administrator role exists in the WordPress installation

A user is affected if the Cart All In One For WooCommerce plugin version 1.1.21 or lower is installed AND the 'Assign page' field is accessible to an administrator user.

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

Immediately update the plugin to a version beyond 1.1.21. If no patched version exists, remove or disable the plugin until a fix is available. As an interim measure, restrict administrator role access and audit user accounts with admin privileges.

Recommended fix High confidence

Cart All In One For WooCommerce version 1.1.22 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Cart All In One For WooCommerce' in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 1.1.22 or later of the plugin
  5. Verify the plugin updated successfully to version 1.1.22 or higher
  6. Test that the 'Assign page' functionality works correctly after the update
Caveat Review plugin changelog for any breaking changes before updating in production environments

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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