dbcve.org
CommerceApplication · Adobe

CVE-2026-34686

HIGH · 8.7 CVSS v3.1 Published 2026-05-12
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.9-beta1, 2.4.8-p4, 2.4.7-p9, 2.4.6-p14, 2.4.5-p16, 2.4.4-p17 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, potentially gaining elevated access or control over the victim's account or session. Scope is changed.

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 · moderate confidence

Stored Cross-Site Scripting (XSS) vulnerability in Adobe Commerce allows low-privileged attackers to inject malicious JavaScript into vulnerable form fields. When victims browse to affected pages, the injected scripts execute in their browsers, potentially enabling session hijacking, account takeover, or privilege escalation.

MitigationApply Adobe's official security patches for this vulnerability and implement proper input validation and output encoding on all user-supplied form fields across the Commerce installation.

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.4.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8= 2.4.9
Commerce B2bApplication
Affected:= 1.3.3= 1.3.4= 1.4.2= 1.5.2= 1.5.3
MagentoCMS
Affected:= 2.4.6= 2.4.7= 2.4.8= 2.4.9

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 version
    Run the command 'php bin/magento --version' or check the composer.json file in the Magento root directory for the 'magento/product-community-edition' version string
    Affected if The version matches 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9
  2. Identify installed Adobe Commerce B2B version
    Check composer.json for 'magento/module-b2b' version or run 'php bin/magento module:status Magento_B2b' to confirm B2B module is enabled
    Affected if The B2B module is installed and its version matches 1.3.3, 1.4.2, 1.5.2, or 1.5.3
  3. Identify installed Adobe Magento version
    Check composer.json for 'magento/magento2-base' version or the version shown in admin panel under System > Configuration > Advanced > Developer
    Affected if The version matches 2.4.6, 2.4.7, 2.4.8, or 2.4.9 (standalone Magento installation)
  4. Locate custom or third-party form modules
    Review the app/code and vendor directories for any custom form implementations or third-party extensions that add form fields to customer-facing or admin-facing pages
    Affected if Custom form handlers exist that may not implement proper output encoding on user-supplied data
  5. Inspect form field rendering for output encoding
    Examine PHP template files (.phtml) and UI component XML files that render form input fields, specifically looking for instances where user-submitted values are displayed without using escape functions such as $block->escapeHtml(), $escaper->escapeHtml(), or htmlspecialchars
    Affected if Form fields render user input without proper HTML encoding or escaping functions

The environment is affected if it runs any of the listed Adobe Commerce, Commerce B2B, or Magento versions AND contains form fields that accept user input without proper output encoding.

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 Adobe's official security patches for this vulnerability and implement proper input validation and output encoding on all user-supplied form fields across the Commerce installation.

Recommended fix Moderate confidence
  1. Check the official Adobe Security Bulletin (APSB26-15) for the specific patch file for your version
  2. Download the applicable security patch from Adobe Commerce portal or Magento Marketplace
  3. Apply the patch following Adobe's standard patch installation process: composer install, then bin/magento setup:upgrade
  4. Clear the cache: bin/magento cache:clean
  5. Verify the patch was applied successfully by checking the patch file in vendor/ and testing the fix in a non-production environment
  6. Deploy to production after validation

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

Fix this in Commerce Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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