dbcve.org
CommerceApplication · Adobe

CVE-2025-47110

HIGH · 8.4 CVSS v3.1 Published 2025-06-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
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.8, 2.4.7-p5, 2.4.6-p10, 2.4.5-p12, 2.4.4-p13 and earlier are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by a high-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. Scope is changed to that of other high-privileged accounts, leading to a high impact on confidentiality, integrity, and availability.

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 allowing high-privileged attackers to inject malicious JavaScript into form fields. When other high-privileged users browse to pages containing the compromised fields, the script executes in their browsers, potentially enabling session hijacking, data theft, or privilege escalation.

MitigationApply Adobe security patches for the affected versions (2.4.8, 2.4.7-p5, 2.4.6-p10, 2.4.5-p12, 2.4.4-p13) or upgrade to patched releases. Additionally, implement input validation and output encoding on vulnerable form fields as identified during the patch application.

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

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

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

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 the installed Adobe Commerce version
    Run the command 'php bin/magento --version' in the Adobe Commerce installation directory, or log into the admin panel and check System > Configuration > General > Advanced > Advanced > Version
    Affected if The version returned is 2.4.4, 2.4.5, 2.4.6, 2.4.7, or 2.4.8
  2. Identify the installed Adobe Commerce B2B version if applicable
    If B2B functionality is present, run 'composer show adobe/commerce-b2b' or check the composer.lock file for the adobe/commerce-b2b package version
    Affected if The B2B version is 1.3.3, 1.3.4, 1.3.5, 1.4.2, or 1.5.2
  3. Confirm admin user access controls
    Log into the admin panel and navigate to System > Permissions > All Users to review high-privilege user accounts, or query the admin_user table in the database for users with role_type = 'G' (Administrators)
    Affected if Multiple high-privileged admin accounts exist with broad system access permissions
  4. Review recent admin activity for anomalous form submissions
    Check admin action logs in the database (admin_action_log table) or Adobe Commerce audit logs for unusual POST requests to form endpoints, particularly look for HTML or script tags in form field data
    Affected if Recent form submissions contain unsanitized HTML, JavaScript tags, or script payloads in fields that were not properly encoded
  5. Inspect stored form data for potential XSS payloads
    Query the database for recent records in key form tables (such as catalog product attributes, customer address fields, or CMS blocks) containing characters like '<script', 'javascript:', or event handlers like 'onerror' or 'onload'
    Affected if Stored database records contain XSS payloads in form fields that would be rendered without proper output encoding

You are affected if your Adobe Commerce or Magento installation runs version 2.4.4 through 2.4.8 (or B2B versions 1.3.3-1.5.2) and contains high-privileged admin accounts with access to vulnerable form fields.

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 security patches for the affected versions (2.4.8, 2.4.7-p5, 2.4.6-p10, 2.4.5-p12, 2.4.4-p13) or upgrade to patched releases. Additionally, implement input validation and output encoding on vulnerable form fields as identified during the patch application.

Recommended fix High confidence

Apply the appropriate security patch: 2.4.4-p13+, 2.4.5-p12+, 2.4.6-p10+, 2.4.7-p5+, or upgrade to 2.4.8+ (if available)

  1. Check your current Adobe Commerce version by running: bin/magento --version or checking composer.json
  2. Identify the corresponding patch version needed: For 2.4.4 apply patch 13 or later, for 2.4.5 apply patch 12 or later, for 2.4.6 apply patch 10 or later, for 2.4.7 apply patch 5 or later
  3. Apply the security patch via composer: composer require magento/product-community-edition=2.4.7-p5 --no-update (adjust version and patch number for your baseline)
  4. Run composer update to install the patched version
  5. Clear the cache: bin/magento cache:flush
  6. Verify the patch was applied by checking the updated version: bin/magento --version
  7. Test the fix in a non-production environment before deploying to production
Caveat Security patches typically do not introduce breaking changes but always test in staging first; ensure PHP and MySQL compatibility for the target version

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

Fix this in Commerce Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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