CVE Intelligence
High Injection

CVE-2023-22731 — Improper Control of Generation of Code in Twig rendered views in shopware

Shopware is an open source commerce platform based on Symfony Framework and Vue js. In a Twig environment **without the Sandbox extension**, it is possible to refer to PHP functions in twig filters like `map`, `filter`, `sort`. This allows a template to call any global PHP function and thus execute arbitrary code. The attacker must have access to a Twig environment in order to exploit this vulnerability. This problem has been fixed with 6.4.18.1 with an override of the specified filters until the integration of the Sandbox extension has been finished. Users are advised to upgrade. Users of major versions 6.1, 6.2, and 6.3 may also receive this fix via a plugin.

Published Jan 17, 2023 · Updated Oct 24, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: GitHub_M

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 1.4% (30-day exploitation probability)+11
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
1.39%
ahead of 72% of scored CVEs · Oct 29, 2026
Affects
Shopware
Platform and 3 more
CVSS base
8.8
High · 4 source(s)
Prioritization reference: 10.0 provisional

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — docs.shopware.com (NIST National Vulnerability Database)
  • Documented patch — github.com (NIST National Vulnerability Database)
  • Composer Shopware/platform: fixed in version 6.4.18.1 — github.com (GitHub Security Advisories)
  • Composer Shopware/core: fixed in version 6.4.18.1 — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Shopware Platform, Shopware Shopware, Composer Shopware/core…).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Shopware Platform version < 6.4.18.1 Vulnerable CVE Program (cve.org) e CISA ADP
Shopware Shopware < 6.4.18.1 Vulnerable NIST National Vulnerability Database
Composer Shopware/core ≤ 6.4.18.0 Vulnerable GitHub Security Advisories
Composer Shopware/platform ≤ 6.4.18.0 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
10.0 CVSS 3.1 Critical — — GitHub_M via CVE Program (cve.org) e CISA ADP
9.9 CVSS 3.1 Critical 3.1 6.0 security-advisories@github.com via NIST National Vulnerability Database
9.8 CVSS 3.1 Critical — — GitHub, Inc. via GitHub Security Advisories
8.8 CVSS 3.1 High 2.8 5.9 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)
Sources assign different scores within the same severity band. For prioritization we use 10.0 (GitHub_M via CVE Program (cve.org) e CISA ADP) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-94 · Code Injection

Other CVEs with this weakness →

EPSS over time FIRST

Oct 23, 2026 → Oct 29, 2026 · 7 reading(s) · max 1.39%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Look for parameters with command/query metacharacters and unexpected child processes of the service.
web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 24, 2026 · GitHub Security Advisories
  • Affected products added · composer/shopware/platform, composer/shopware/core
    Oct 24, 2026 · GitHub Security Advisories
  • Affected products added · shopware/platform
    Oct 24, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 24, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 24, 2026
  • Fix documented
    Oct 24, 2026 · NIST National Vulnerability Database
  • Affected products added · shopware/shopware
    Oct 24, 2026 · NIST National Vulnerability Database
  • CVSS changed · 8.8
    Oct 24, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 24, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 24, 2026 · Alertas do Telegram
  • 2023
  • CVE published
    Jan 17, 2023 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 24, 2026 – Oct 24, 2026
  • 1× Official description updated · Oct 24, 2026 – Oct 24, 2026

References

5 on the record

Elsewhere on this site

Shopware
every CVE for this vendor
Injection
same class
CWE-94
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-104937 CVE-2026-104937 17d
  • CVE-2026-48013 Shopware: SSRF in Media External-Link Endpoint Bypasses IP Validation Jul 23, 2026
  • CVE-2026-48012 Shopware SSO referer trust leading to an arbitrary redirect target Jul 23, 2026
  • CVE-2026-48014 Shopware: Admin API ACL Bypass in Order State Transition Endpoints Jul 17, 2026
  • CVE-2026-48010 Shopware: Privilege escalation: non-admin user with user:create ACL can create admin accounts Jul 17, 2026
  • CVE-2026-48016 Shopware: Unauthorized Payment Trigger for Foreign Orders via /store-api/handle-payment Jul 17, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2023-22731 is "Improper Control of Generation of Code in Twig rendered views in shopware", rated High. It affects Platform (Shopware); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.8 describes technical severity. EPSS 1.39% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.