CVE-2026-2019
Received Received - Intake
Code Injection in Cart All In One WooCommerce Plugin Allows PHP Execution

Publication date: 2026-02-18

Last updated on: 2026-02-18

Assigner: Wordfence

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-18
Last Modified
2026-02-18
Generated
2026-05-07
AI Q&A
2026-02-18
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 3 associated CPEs
Vendor Product Version / Range
wordfence woo-cart-all-in-one to 1.1.21 (inc)
wordfence woo-cart-all-in-one 1.1.2
wordfence woo-cart-all-in-one 1.1.22
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-74 The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

[{'type': 'paragraph', 'content': "The vulnerability in the Cart All In One For WooCommerce WordPress plugin (up to version 1.1.21) is a code injection flaw caused by insufficient input validation on the 'Assign page' field. This field's content is passed directly to the PHP eval() function without proper sanitization, allowing authenticated users with Administrator-level access or higher to execute arbitrary PHP code on the server."}, {'type': 'paragraph', 'content': 'The issue arises because the plugin evaluates user-defined conditional logic using eval(), which can be exploited if malicious code is injected. Although a later update (version 1.1.22) introduced restrictions by whitelisting specific WordPress conditional functions and added input validation, the fundamental use of eval() remains a critical security risk.'}] [3]


How can this vulnerability impact me? :

This vulnerability can have severe impacts because it allows an authenticated administrator to execute arbitrary PHP code on the server hosting the WordPress site. This can lead to full compromise of the server, including data theft, site defacement, installation of backdoors, or further attacks on the hosting environment.

Since the attacker must have Administrator-level access, the risk is primarily from insiders or attackers who have already gained elevated privileges. However, exploiting this vulnerability could allow privilege escalation or persistent control over the site.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

[{'type': 'paragraph', 'content': 'This vulnerability can be detected by checking if the WooCommerce plugin "Cart All In One For WooCommerce" is installed and running a version up to and including 1.1.21, as these versions contain the vulnerable code.'}, {'type': 'paragraph', 'content': "Since the vulnerability involves unsafe use of the PHP eval() function on the 'Assign page' field, detection can include searching for suspicious or unexpected PHP code execution or modifications in the plugin settings related to this field."}, {'type': 'paragraph', 'content': 'On the system, you can check the plugin version by running commands to list installed WordPress plugins and their versions, for example:'}, {'type': 'list_item', 'content': 'wp plugin list --path=/path/to/wordpress | grep woo-cart-all-in-one'}, {'type': 'paragraph', 'content': "To detect potential exploitation attempts, you can search web server logs for POST requests or admin actions modifying the 'Assign page' field or containing suspicious PHP code patterns."}, {'type': 'paragraph', 'content': "Additionally, scanning the plugin files for the presence of eval() usage in the relevant files (e.g., in the code handling the 'Assign page' option) can help identify vulnerable versions."}] [3]


What immediate steps should I take to mitigate this vulnerability?

[{'type': 'paragraph', 'content': 'The immediate mitigation step is to update the "Cart All In One For WooCommerce" plugin to version 1.1.22 or later, where the vulnerability has been partially mitigated by restricting the allowed conditional tags and adding input validation before using eval().'}, {'type': 'paragraph', 'content': "If updating immediately is not possible, restrict administrator access to the plugin settings, especially the 'Assign page' field, to prevent exploitation by limiting who can input potentially malicious code."}, {'type': 'paragraph', 'content': 'Monitor and audit administrator actions related to this plugin to detect any suspicious changes.'}, {'type': 'paragraph', 'content': 'Consider disabling or removing the plugin if it is not essential, to eliminate the attack surface.'}] [3]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart