Security readout for executives and security teams
Plain-English summary
This flaw lets a logged-in WordPress administrator inject PHP code through a Cart All In One For WooCommerce setting. Because administrator access is required, it is not an unauthenticated break-in. However, if an admin account is compromised, the issue can turn that access into full server-side code execution.
Executive priority
Prioritize remediation on production ecommerce sites, especially where admin accounts are broadly shared or weakly protected. This is high impact but requires administrator access, so pair patching with administrator account hardening and review for suspicious changes.
Technical view
Cart All In One For WooCommerce versions up to and including 1.1.21 insufficiently validate the 'Assign page' setting, which is passed to PHP eval(). Wordfence rates it CVSS 7.2 high. Required privileges are Administrator or higher, with network access and no user interaction. CWE-74 is listed.
Likely exposure
Exposure is limited to WordPress sites running the Cart All In One For WooCommerce plugin at version 1.1.21 or earlier. Practical risk is highest where many users have administrator privileges, admin accounts lack MFA, or site administration is exposed to untrusted networks.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation requires authenticated Administrator-level access, but successful use could execute arbitrary PHP code on the web server with serious confidentiality, integrity, and availability impact.
Researcher notes
Evidence identifies eval() use on the Assign page setting and a WordPress Trac changeset. The bundle does not provide a clearly named fixed version, exploit-in-the-wild confirmation, or vendor advisory text beyond referenced public records. Treat fixed-version determination as something to verify from WordPress.org/plugin vendor sources.
Mitigation direction
- Inventory WordPress sites for the woo-cart-all-in-one plugin and version.
- Update the plugin following vendor or WordPress.org guidance.
- Review the referenced WordPress Trac changeset for the relevant code correction.
- Restrict WordPress administrator accounts to necessary personnel only.
- Enable MFA and strong credential controls for administrator accounts.
- Temporarily disable the plugin if updating is unavailable and risk is unacceptable.
Validation and detection
- Confirm whether Cart All In One For WooCommerce is installed.
- Check plugin version and flag 1.1.21 or earlier.
- Review administrator user list for unexpected or excessive privileges.
- Check recent changes to the plugin's Assign page setting.
- Review web and WordPress logs for suspicious administrator activity.
- Verify the vulnerable eval-based path is removed after updating.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-2019 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/25bdb89f-3478-4a1a-8bf0-46e88207eb21?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/woo-cart-all-in-one/trunk/includes/frontend/sidebar-cart-icon.php#L245CVE reference
- https://plugins.trac.wordpress.org/browser/woo-cart-all-in-one/tags/1.1.21/includes/frontend/sidebar-cart-icon.php#L245CVE reference
- https://plugins.trac.wordpress.org/changeset/3455202/CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
