CVE-2025-54236: Adobe Commerce and Magento Improper Input Validation Vulnerability

Published Sep 9, 2025
·
Updated

Adobe Commerce and Magento Open Source contain an improper input validation vulnerability that could allow an attacker to take over customer accounts through the Commerce REST API.

Other sources

Adobe Commerce versions 2.4.9-alpha2, 2.4.8-p2, 2.4.7-p7, 2.4.6-p12, 2.4.5-p14, 2.4.4-p15 and earlier are affected by an Improper Input Validation vulnerability that could result in a Security feature bypass. A successful attacker can abuse this to achieve session takeover, increasing the confidentiality and integrity impact to high. Exploitation of this issue does not require user interaction.

GitHub

Adobe Commerce versions 2.4.9-alpha2, 2.4.8-p2, 2.4.7-p7, 2.4.6-p12, 2.4.5-p14, 2.4.4-p15 and earlier are affected by an Improper Input Validation vulnerability. A successful attacker can abuse this to achieve session takeover, increasing the confidentiality, and integrity impact to high. Exploitation of this issue does not require user interaction.

NVD

Affected Software

165 affected components
Adobe Commerce<2.4.9-alpha2
composer/magento/project-community-edition<=2.0.2
composer/magento/community-edition=2.4.9
composer/magento/community-edition>=2.4.8-beta1<=2.4.8-p2
composer/magento/community-edition>=2.4.7-beta1<=2.4.7-p7
composer/magento/community-edition=2.4.8
composer/magento/community-edition=2.4.7
composer/magento/community-edition>=2.4.9-alpha1<=2.4.9-alpha2
composer/magento/community-edition=2.4.5
composer/magento/community-edition>=2.4.6-p1<=2.4.6-p12
composer/magento/community-edition=2.4.6
composer/magento/community-edition<=2.4.5-p14
Adobe Commerce=2.4.4
Adobe Commerce=2.4.4-p1
Adobe Commerce=2.4.4-p10
Adobe Commerce=2.4.4-p11
Adobe Commerce=2.4.4-p12
Adobe Commerce=2.4.4-p13
Adobe Commerce=2.4.4-p14
Adobe Commerce=2.4.4-p15
Adobe Commerce=2.4.4-p2
Adobe Commerce=2.4.4-p3
Adobe Commerce=2.4.4-p4
Adobe Commerce=2.4.4-p5
Adobe Commerce=2.4.4-p6
Adobe Commerce=2.4.4-p7
Adobe Commerce=2.4.4-p8
Adobe Commerce=2.4.4-p9
Adobe Commerce=2.4.5
Adobe Commerce=2.4.5-p1
Adobe Commerce=2.4.5-p10
Adobe Commerce=2.4.5-p11
Adobe Commerce=2.4.5-p12
Adobe Commerce=2.4.5-p13
Adobe Commerce=2.4.5-p14
Adobe Commerce=2.4.5-p2
Adobe Commerce=2.4.5-p3
Adobe Commerce=2.4.5-p4
Adobe Commerce=2.4.5-p5
Adobe Commerce=2.4.5-p6
Adobe Commerce=2.4.5-p7
Adobe Commerce=2.4.5-p8
Adobe Commerce=2.4.5-p9
Adobe Commerce=2.4.6
Adobe Commerce=2.4.6-p1
Adobe Commerce=2.4.6-p10
Adobe Commerce=2.4.6-p11
Adobe Commerce=2.4.6-p12
Adobe Commerce=2.4.6-p2
Adobe Commerce=2.4.6-p3
Adobe Commerce=2.4.6-p4
Adobe Commerce=2.4.6-p5
Adobe Commerce=2.4.6-p6
Adobe Commerce=2.4.6-p7
Adobe Commerce=2.4.6-p8
Adobe Commerce=2.4.6-p9
Adobe Commerce=2.4.7
Adobe Commerce=2.4.7-b1
Adobe Commerce=2.4.7-b2
Adobe Commerce=2.4.7-beta3
Adobe Commerce=2.4.7-p1
Adobe Commerce=2.4.7-p2
Adobe Commerce=2.4.7-p3
Adobe Commerce=2.4.7-p4
Adobe Commerce=2.4.7-p5
Adobe Commerce=2.4.7-p6
Adobe Commerce=2.4.7-p7
Adobe Commerce=2.4.8
Adobe Commerce=2.4.8-beta1
Adobe Commerce=2.4.8-beta2
Adobe Commerce=2.4.8-p1
Adobe Commerce=2.4.8-p2
Adobe Commerce=2.4.9-alpha1
Adobe Commerce=2.4.9-alpha2
Adobe Commerce B2b=1.3.3
Adobe Commerce B2b=1.3.3-p1
Adobe Commerce B2b=1.3.3-p10
Adobe Commerce B2b=1.3.3-p11
Adobe Commerce B2b=1.3.3-p12
Adobe Commerce B2b=1.3.3-p13
Adobe Commerce B2b=1.3.3-p14
Adobe Commerce B2b=1.3.3-p15
Adobe Commerce B2b=1.3.3-p2
Adobe Commerce B2b=1.3.3-p3
Adobe Commerce B2b=1.3.3-p4
Adobe Commerce B2b=1.3.3-p5
Adobe Commerce B2b=1.3.3-p6
Adobe Commerce B2b=1.3.3-p7
Adobe Commerce B2b=1.3.3-p8
Adobe Commerce B2b=1.3.3-p9
Adobe Commerce B2b=1.3.4
Adobe Commerce B2b=1.3.4-p1
Adobe Commerce B2b=1.3.4-p10
Adobe Commerce B2b=1.3.4-p11
Adobe Commerce B2b=1.3.4-p12
Adobe Commerce B2b=1.3.4-p13
Adobe Commerce B2b=1.3.4-p14
Adobe Commerce B2b=1.3.4-p2
Adobe Commerce B2b=1.3.4-p3
Adobe Commerce B2b=1.3.4-p4
Adobe Commerce B2b=1.3.4-p5
Adobe Commerce B2b=1.3.4-p6
Adobe Commerce B2b=1.3.4-p7
Adobe Commerce B2b=1.3.4-p8
Adobe Commerce B2b=1.3.4-p9
Adobe Commerce B2b=1.4.2
Adobe Commerce B2b=1.4.2-p1
Adobe Commerce B2b=1.4.2-p2
Adobe Commerce B2b=1.4.2-p3
Adobe Commerce B2b=1.4.2-p4
Adobe Commerce B2b=1.4.2-p5
Adobe Commerce B2b=1.4.2-p6
Adobe Commerce B2b=1.4.2-p7
Adobe Commerce B2b=1.5.2
Adobe Commerce B2b=1.5.2-p1
Adobe Commerce B2b=1.5.2-p2
Adobe Commerce B2b=1.5.3-alpha1
Adobe Commerce B2b=1.5.3-alpha2
Adobe Magento=2.4.5
Adobe Magento=2.4.5-p1
Adobe Magento=2.4.5-p10
Adobe Magento=2.4.5-p11
Adobe Magento=2.4.5-p12
Adobe Magento=2.4.5-p13
Adobe Magento=2.4.5-p14
Adobe Magento=2.4.5-p2
Adobe Magento=2.4.5-p3
Adobe Magento=2.4.5-p4
Adobe Magento=2.4.5-p5
Adobe Magento=2.4.5-p6
Adobe Magento=2.4.5-p7
Adobe Magento=2.4.5-p8
Adobe Magento=2.4.5-p9
Adobe Magento=2.4.6
Adobe Magento=2.4.6-p1
Adobe Magento=2.4.6-p10
Adobe Magento=2.4.6-p11
Adobe Magento=2.4.6-p12
Adobe Magento=2.4.6-p2
Adobe Magento=2.4.6-p3
Adobe Magento=2.4.6-p4
Adobe Magento=2.4.6-p5
Adobe Magento=2.4.6-p6
Adobe Magento=2.4.6-p7
Adobe Magento=2.4.6-p8
Adobe Magento=2.4.6-p9
Adobe Magento=2.4.7
Adobe Magento=2.4.7-b1
Adobe Magento=2.4.7-b2
Adobe Magento=2.4.7-beta3
Adobe Magento=2.4.7-p1
Adobe Magento=2.4.7-p2
Adobe Magento=2.4.7-p3
Adobe Magento=2.4.7-p4
Adobe Magento=2.4.7-p5
Adobe Magento=2.4.7-p6
Adobe Magento=2.4.7-p7
Adobe Magento=2.4.8
Adobe Magento=2.4.8-beta1
Adobe Magento=2.4.8-beta2
Adobe Magento=2.4.8-p1
Adobe Magento=2.4.8-p2
Adobe Magento=2.4.9-alpha1
Adobe Magento=2.4.9-alpha2
Adobe Commerce and Magento

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Remove

    Remove composer/magento/community-edition from your environment.

    Discontinue use of the product or uninstall if vendor mitigations are unavailable for the Improper Input Validation vulnerability.

  2. Remove

    Remove composer/magento/project-community-edition from your environment.

    Discontinue use of the product or uninstall if vendor mitigations are unavailable for the Improper Input Validation vulnerability.

  3. Compensating control

    Apply mitigations per vendor instructions for the Improper Input Validation vulnerability. Follow applicable BOD 22-01 guidance for cloud services.

Event History

Sep 9, 2025
CVE Published
via MITRE·01:20 PM
Data Sourced
via MITRE·01:20 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:15 PM
DescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·03:31 PM
Data Sourced
via GitHub·03:31 PM
DescriptionSeverityWeaknessAffected Software
News Published
via BleepingComputer·03:53 PM
News Published
via BleepingComputer·03:55 PM
Oct 22, 2025
News Published
via BleepingComputer·06:41 PM
Oct 24, 2025
Known Exploited
via CISA·12:00 AM
Data Sourced
via CISA·12:00 AM
RemedyDescriptionAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-54236?

CVE-2025-54236 is considered a high-severity vulnerability due to its potential for security feature bypass and session takeover.

2

How do I fix CVE-2025-54236?

To fix CVE-2025-54236, upgrade your Adobe Commerce installation to version 2.4.9-alpha3 or later, or apply any available security patches.

3

What versions of Adobe Commerce are affected by CVE-2025-54236?

Adobe Commerce versions 2.4.9-alpha2, 2.4.8-p2, 2.4.7-p7, 2.4.6-p12, 2.4.5-p14, and 2.4.4-p15 and earlier are affected by CVE-2025-54236.

4

Can CVE-2025-54236 lead to data breaches?

Yes, CVE-2025-54236 can potentially lead to data breaches through session takeover if exploited by an attacker.

5

What can I do to protect against CVE-2025-54236?

To protect against CVE-2025-54236, ensure your Adobe Commerce software is updated to the latest version and monitor for suspicious activity.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203