Skip to content
Noroxi
CVE-2024-45127· NVD / CVE Program· CNA adobe

Adobe Commerce | Cross-site Scripting (Stored XSS) (CWE-79)

Adobe Commerce versions 2.4.7-p2, 2.4.6-p7, 2.4.5-p9, 2.4.4-p10 and earlier are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by an admin 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.

MediumCVSS 4.8 · v3.1—No exploit Fix available
Published
Oct 10, 2024
Updated
Jun 17, 2026
EPSS
0.5% · 40th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

19

Monitor

Low priority for now.

CVSS
19 / 40 · 4.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · adobe
4.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
adobecommerce
adobecommerce b2b
adobemagento

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • adobe commerceall versions
  • adobe commerce2.3.7
  • adobe commerce2.4.0
  • adobe commerce2.4.1
  • adobe commerce2.4.2
  • adobe commerce2.4.3
  • adobe commerce2.4.4
  • adobe commerce2.4.5
  • adobe commerce2.4.6
  • adobe commerce2.4.7
  • adobe commerce b2b1.3.3
  • adobe commerce b2b1.3.4
  • adobe commerce b2b1.3.5
  • adobe commerce b2b1.4.2
  • adobe magentoall versions
  • adobe magento2.4.3
  • adobe magento2.4.4
  • adobe magento2.4.5
  • adobe magento2.4.6
  • adobe magento2.4.7

Versions reported by the vendor

Affected version ranges reported by the assigning authority (adobe). Independent of NVD's CPE analysis and usually ahead of it.

  • Adobe Adobe Commerce

    • up to and including 2.4.4-p10affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Packagistmagento/community-editionfrom 2.4.5-p1 · before 2.4.5-p102.4.5-p10
Packagistmagento/community-editionfrom 2.4.6-p1 · before 2.4.6-p82.4.6-p8
Packagistmagento/community-editionfrom 2.4.7-beta1 · before 2.4.7-p32.4.7-p3
Packagistmagento/community-editionbefore 2.4.4-p112.4.4-p11
Packagistmagento/community-editionall versions—

Other highest-scoring records for the same primary product.

  • CVE-2024-34102XXE can expose crypt key and other secrets granting full admin accessKEV
    99Now
  • CVE-2022-24086Adobe Commerce checkout improper input validation leads to remote code executionKEV
    99Now
  • CVE-2025-54236Adobe Commerce | Improper Input Validation (CWE-20)KEV
    94Now
  • CVE-2026-71362Adobe Commerce | Incorrect Authorization (CWE-863)KEV
    92Now
  • CVE-2026-75650Adobe Commerce | Improper Neutralization of Special Elements Used in a Template Engine (CWE-1336)KEV
    71This week
  • CVE-2025-24434Adobe Commerce | Incorrect Authorization (CWE-863)
    41Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Packagist:magento/community-edition2.4.4-p11Package registry (OSV)
Packagist:magento/community-edition2.4.5-p10Package registry (OSV)
Packagist:magento/community-edition2.4.6-p8Package registry (OSV)
Packagist:magento/community-edition2.4.7-p3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2024-20719238 days apart[Adobe Commerce] Stored XSS from low privileged admin user on every admin page, bypassing CVE-2023-29297
    36Monitor
  • CVE-2025-24413124 days apartAdobe Commerce | Cross-site Scripting (Stored XSS) (CWE-79)
    34Monitor
  • CVE-2025-24415124 days apartAdobe Commerce | Cross-site Scripting (Stored XSS) (CWE-79)
    34Monitor
  • CVE-2025-24416124 days apartAdobe Commerce | Cross-site Scripting (Stored XSS) (CWE-79)
    34Monitor
  • CVE-2025-24417124 days apartAdobe Commerce | Cross-site Scripting (Stored XSS) (CWE-79)
    34Monitor
  • CVE-2025-24438124 days apartAdobe Commerce | Cross-site Scripting (Stored XSS) (CWE-79)
    34Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • Administrator privileges are required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
Required
Scope
Changed
Confidentiality impact
Low
Integrity impact
Low
Availability impact
None

CVSS vector

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

nvd-secondary

Root cause

User content is inserted into the page as HTML. The browser interprets the content as code rather than data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
commentEl.innerHTML = comment.body;

Fixed

ts
commentEl.textContent = comment.body;

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records