CVE-2025-49559: Magento vulnerable to path traversal

Published Aug 12, 2025
·
Updated

Adobe 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 an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability that could result in a security feature bypass. An attacker could leverage this vulnerability to modify limited data. Exploitation of this issue does not require user interaction.

Other sources

Magento 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 an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability that could result in a security feature bypass. An attacker could leverage this vulnerability to modify limited data. Exploitation of this issue does not require user interaction.

— GitHub

Affected Software

169 affected componentsFixes available
Adobe Commerce<2.4.9-alpha1
Adobe Commerce<2.4.4
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-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-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-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.8
Adobe Commerce=2.4.8-beta1
Adobe Magento<2.4.5
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-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-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.8
Adobe Magento=2.4.8-beta1
Adobe Magento=2.4.8-beta2
Adobe Magento=2.4.8-p1
Adobe Magento=2.4.9-alpha1
Adobe Commerce B2b<1.3.3
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-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-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.3.5
Adobe Commerce B2b=1.3.5-p1
Adobe Commerce B2b=1.3.5-p10
Adobe Commerce B2b=1.3.5-p11
Adobe Commerce B2b=1.3.5-p2
Adobe Commerce B2b=1.3.5-p3
Adobe Commerce B2b=1.3.5-p4
Adobe Commerce B2b=1.3.5-p5
Adobe Commerce B2b=1.3.5-p6
Adobe Commerce B2b=1.3.5-p7
Adobe Commerce B2b=1.3.5-p8
Adobe Commerce B2b=1.3.5-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.5.2
Adobe Commerce B2b=1.5.2-p1
Adobe Commerce B2b=1.5.3-alpha1
composer/magento/project-community-edition<=2.0.2
composer/magento/community-edition=2.4.8
composer/magento/community-edition=2.4.7
composer/magento/community-edition=2.4.6
composer/magento/community-edition=2.4.5
composer/magento/community-edition<2.4.5-p14
2.4.5-p14
composer/magento/community-edition>=2.4.6-p1, <2.4.6-p12
2.4.6-p12
composer/magento/community-edition>=2.4.7-beta1, <2.4.7-p7
2.4.7-p7
composer/magento/community-edition>=2.4.8-beta1, <2.4.8-p2
2.4.8-p2
composer/magento/community-edition>=2.4.9-alpha1, <2.4.9-alpha2
2.4.9-alpha2
composer/magento/community-edition=2.4.8
composer/magento/community-edition=2.4.7
composer/magento/community-edition=2.4.6
composer/magento/community-edition=2.4.5
composer/magento/community-edition<2.4.5-p14
2.4.5-p14
composer/magento/community-edition>=2.4.6-p1<2.4.6-p12
2.4.6-p12
composer/magento/community-edition>=2.4.7-beta1<2.4.7-p7
2.4.7-p7
composer/magento/community-edition>=2.4.8-beta1<2.4.8-p2
2.4.8-p2
composer/magento/community-edition>=2.4.9-alpha1<2.4.9-alpha2
2.4.9-alpha2
composer/magento/project-community-edition<=2.0.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/magento/community-edition to a version that resolves this vulnerability.

    Fixed in 2.4.5-p14
  2. Upgrade

    Upgrade composer/magento/community-edition to a version that resolves this vulnerability.

    Fixed in 2.4.6-p12
  3. Upgrade

    Upgrade composer/magento/community-edition to a version that resolves this vulnerability.

    Fixed in 2.4.7-p7
  4. Upgrade

    Upgrade composer/magento/community-edition to a version that resolves this vulnerability.

    Fixed in 2.4.8-p2
  5. Upgrade

    Upgrade composer/magento/community-edition to a version that resolves this vulnerability.

    Fixed in 2.4.9-alpha2

Event History

Aug 12, 2025
CVE Published
via MITRE·05:55 PM
Data Sourced
via MITRE·05:55 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·06:31 PM
Data Sourced
via GitHub·06:31 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via Packagist·06:31 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-49559?

CVE-2025-49559 is considered a high severity vulnerability due to its potential to allow path traversal attacks.

2

How do I fix CVE-2025-49559?

To fix CVE-2025-49559, upgrade Adobe Commerce to version 2.4.9-alpha2 or later.

3

What types of attacks does CVE-2025-49559 enable?

CVE-2025-49559 could allow attackers to bypass security features and access restricted directories.

4

Who is affected by CVE-2025-49559?

Adobe 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 CVE-2025-49559.

5

What details are known about the CVE-2025-49559 exploit?

CVE-2025-49559 is an improper limitation of pathname vulnerability that may allow unauthorized file access.

Company

Resources

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