CVE-2025-49555
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 · uneditedAdobe Commerce versions 2.4.9-alpha1, 2.4.8-p1, 2.4.7-p6, 2.4.6-p11, 2.4.5-p13, 2.4.4-p14 and earlier are affected by a Cross-Site Request Forgery (CSRF) vulnerability that could result in privilege escalation. A high-privileged attacker could trick a victim into executing unintended actions on a web application where the victim is authenticated, potentially allowing unauthorized access or modification of sensitive data. Exploitation of this issue requires user interaction in that a victim must visit a malicious website or click on a crafted link. 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 · high confidenceAdobe Commerce contains a CSRF vulnerability allowing high-privileged attackers to trick authenticated administrators into executing unintended administrative actions. The attack requires user interaction (visiting malicious site or clicking crafted link) and can lead to privilege escalation and unauthorized data access/modification. The changed scope indicates impact extends beyond the originally vulnerable component.
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< 2.4.4= 2.4.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8< 1.3.3= 1.3.3= 1.3.4= 1.3.5= 1.4.2= 1.5.2= 1.5.3< 2.4.5= 2.4.5= 2.4.6= 2.4.7= 2.4.8= 2.4.9CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Adobe Commerce or Magento versionCheck the version file in your installation directory (typically composer.json or app/etc/app.xml) or log into the admin panel and navigate to System > Settings > Advanced > Admin > Version (or similar version display area in System > About System).Affected if The installed version matches any of the affected versions listed: Adobe Commerce < 2.4.4, 2.4.4 through 2.4.8; Adobe Commerce B2b < 1.3.3, 1.3.3 through 1.5.3; Adobe Magento < 2.4.5, 2.4.5 through 2.4.9.
-
Confirm admin panel is network-accessibleVerify whether the admin interface (usually at /admin or /backend) is exposed to untrusted networks or the internet. Check your web server configuration and firewall rules for any paths matching 'admin' that are accessible externally.Affected if The admin panel is reachable from untrusted networks, making authenticated administrators susceptible to phishing attacks.
-
Inspect admin forms for CSRF token presenceAccess the admin panel and examine the HTML source of state-changing forms (such as user management, configuration save, or catalog operations). Look for a hidden input field containing a token value, typically named 'form_key', 'csrf_token', or similar, and verify it is submitted with form posts.Affected if Admin forms lack a unique CSRF token in each form submission, or the same token is reused across sessions.
-
Verify Origin or Referer header validation on admin actionsReview your web server logs or application code when admin actions are triggered. Check if the application validates the Origin or Referer HTTP headers to confirm requests originate from the legitimate admin domain.Affected if The application does not validate the Origin or Referer headers on state-changing admin requests.
You are affected if your Adobe Commerce or Magento version falls within the affected ranges AND the admin panel is accessible, AND your admin forms lack CSRF token protection or header validation.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.3.32.4.42.4.5
Implement anti-CSRF tokens (synchronizer token pattern) on all state-changing admin actions and validate the Origin/Referer headers. Apply the vendor security patch and educate administrators about not clicking untrusted links.
Adobe Commerce 2.4.7-p1 or later (latest 2.4.x stable release); Adobe Commerce B2B 1.3.6 or later
- 1. Identify the current Adobe Commerce/Magento version installed by checking the admin panel or running `php bin/magento --version`
- 2. Review the Adobe Commerce release calendar at helpx.adobe.com for the latest security patches addressing CVE-2025-49555
- 3. Create a full backup of the Magento database and filesystem before proceeding with any upgrade
- 4. Put the Magento application into maintenance mode using `php bin/magento maintenance:enable`
- 5. Upgrade to Adobe Commerce 2.4.7-p1 or later (or the latest 2.4.x release) using Composer: `composer require magento/product-community-edition=2.4.7-p1 --no-update` followed by `composer update`
- 6. For Adobe Commerce B2b users, ensure the B2B extension is also upgraded to version 1.3.6 or later to address the vulnerability in B2B modules
- 7. Run the upgrade scripts: `php bin/magento setup:upgrade`
- 8. Clear the cache: `php bin/magento cache:flush`
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49555 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-49555 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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