dbcve.org
CommerceApplication · Adobe

CVE-2023-38219

HIGH · 8.7 CVSS v3.1 Published 2023-10-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable

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
Adobe Commerce versions 2.4.7-beta1 (and earlier), 2.4.6-p2 (and earlier), 2.4.5-p4 (and earlier) and 2.4.4-p5 (and earlier) are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by a low-privileged attacker to inject malicious scripts into vulnerable form fields. Malicious JavaScript may be executed in a victim’s browser when they browse to the page containing the vulnerable field. Payload is stored in an admin area, resulting in high confidentiality and integrity impact.

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

Stored Cross-Site Scripting (XSS) vulnerability in Adobe Commerce admin area allows low-privilege attackers to inject malicious JavaScript into form fields. The payload is stored in the database and executes when administrators browse to affected pages, leading to high confidentiality and integrity impact.

MitigationApply vendor-provided security patches or upgrade to a fixed Adobe Commerce version. Implement proper input validation and output encoding on affected admin form fields.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CommerceApplication
Affected:= 2.3.7= 2.4.0= 2.4.1= 2.4.2= 2.4.3= 2.4.4= 2.4.5= 2.4.6= 2.4.7
MagentoCMS
Affected:= 2.4.4= 2.4.5= 2.4.6= 2.4.7

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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N

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. Identify installed Adobe Commerce or Magento version
    Run the command: php bin/magento --version or check the composer.json file in the installation root for the 'version' or 'magento/product-community-edition' package version
    Affected if The version matches 2.3.7, 2.4.0, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 2.4.5, 2.4.6, or 2.4.7 for Adobe Commerce; or 2.4.4, 2.4.5, 2.4.6, or 2.4.7 for Magento Open Source
  2. Confirm admin panel is accessible
    Verify the /admin or custom admin URL is reachable and loggable by checking the app/etc/env.php file for the backend frontName setting, then attempt to access the admin login page
    Affected if The admin panel is exposed and accessible to the user (even if credentials are not known, the endpoint existence matters for exposure)
  3. Inspect stored data in admin-related database tables
    Query the database for potentially malicious scripts in tables that store admin form data, such as: SELECT * FROM admin_user WHERE additional_roles LIKE '%<script%' OR SELECT * FROM adminnotification_inbox WHERE description LIKE '%<script%' (adjust table names based on actual schema)
    Affected if Any records contain unsanitized HTML or JavaScript tags like <script>, <img onerror=>, or javascript: URIs that were not properly encoded upon storage

You are affected if your Adobe Commerce or Magento version matches one of the listed affected versions AND the admin panel is accessible and contains unsanitized script content in database tables that are rendered in admin pages.

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

Apply vendor-provided security patches or upgrade to a fixed Adobe Commerce version. Implement proper input validation and output encoding on affected admin form fields.

Recommended fix Moderate confidence

Magento 2.4.4-p6 or later; 2.4.5-p5 or later; 2.4.6-p3 or later; 2.4.7-p1 or later (latest stable 2.4.7-x)

  1. 1. Back up the Adobe Commerce/Magento database and file system
  2. 2. Review the current installed version using bin/magento --version or composer show magento/product-community-edition
  3. 3. For Magento 2.4.4: Upgrade to 2.4.4-p6 or later using composer require magento/product-community-edition=2.4.4-p6 --no-update followed by composer update
  4. 4. For Magento 2.4.5: Upgrade to 2.4.5-p5 or later using composer require magento/product-community-edition=2.4.5-p5 --no-update followed by composer update
  5. 5. For Magento 2.4.6: Upgrade to 2.4.6-p3 or later using composer require magento/product-community-edition=2.4.6-p3 --no-update followed by composer update
  6. 6. For Magento 2.4.7: Upgrade to 2.4.7-p1 or later (or the latest stable 2.4.7-x release)
  7. 7. Run bin/magento setup:upgrade to apply database migrations
  8. 8. Clear caches using bin/magento cache:flush
Caveat Standard upgrade considerations apply: review extension compatibility, test custom themes/templates, verify third-party module compatibility with the new patch version before production deployment

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

Fix this in Commerce Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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