CVE-2025-49559
Unknown
Unknown - Not Provided
BaseFortify
Publication date: 2025-08-12
Last updated on: 2025-08-15
Assigner: Adobe Systems Incorporated
Description
Description
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.
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| adobe | commerce | 2.4.6 |
| adobe | commerce | 2.4.6 |
| adobe | commerce | 2.4.6 |
| adobe | commerce | 2.4.6 |
| adobe | commerce | 2.4.6 |
| adobe | commerce | 2.4.7 |
| adobe | commerce | 2.4.7 |
| adobe | commerce | 2.4.7 |
| adobe | commerce | 2.4.7 |
| adobe | commerce | 2.4.7 |
| adobe | commerce | 2.4.7 |
| adobe | commerce | 2.4.7 |
| adobe | commerce | 2.4.7 |
| adobe | commerce | 2.4.7 |
| adobe | commerce | 2.4.7 |
| adobe | commerce | 2.4.8 |
| adobe | commerce | 2.4.8 |
| adobe | magento | to 2.4.5 (exc) |
| adobe | magento | 2.4.5 |
| adobe | magento | 2.4.5 |
| adobe | magento | 2.4.5 |
| adobe | magento | 2.4.5 |
| adobe | magento | 2.4.5 |
| adobe | magento | 2.4.5 |
| adobe | magento | 2.4.5 |
| adobe | magento | 2.4.5 |
| adobe | magento | 2.4.5 |
| adobe | magento | 2.4.5 |
| adobe | magento | 2.4.5 |
| adobe | magento | 2.4.5 |
| adobe | magento | 2.4.5 |
| adobe | magento | 2.4.5 |
| adobe | magento | 2.4.6 |
| adobe | magento | 2.4.6 |
| adobe | magento | 2.4.6 |
| adobe | magento | 2.4.6 |
| adobe | magento | 2.4.6 |
| adobe | magento | 2.4.6 |
| adobe | magento | 2.4.6 |
| adobe | magento | 2.4.6 |
| adobe | magento | 2.4.6 |
| adobe | magento | 2.4.6 |
| adobe | magento | 2.4.6 |
| adobe | magento | 2.4.6 |
| adobe | magento | 2.4.7 |
| adobe | magento | 2.4.7 |
| adobe | magento | 2.4.7 |
| adobe | magento | 2.4.7 |
| adobe | magento | 2.4.7 |
| adobe | magento | 2.4.7 |
| adobe | magento | 2.4.7 |
| adobe | magento | 2.4.7 |
| adobe | magento | 2.4.7 |
| adobe | magento | 2.4.7 |
| adobe | magento | 2.4.8 |
| adobe | magento | 2.4.8 |
| adobe | magento | 2.4.8 |
| adobe | magento | 2.4.8 |
| adobe | magento | 2.4.9 |
| adobe | commerce_b2b | to 1.3.3 (exc) |
| adobe | commerce_b2b | 1.3.3 |
| adobe | commerce_b2b | 1.3.3 |
| adobe | commerce_b2b | 1.3.3 |
| adobe | commerce_b2b | 1.3.3 |
| adobe | commerce_b2b | 1.3.3 |
| adobe | commerce_b2b | 1.3.3 |
| adobe | commerce_b2b | 1.3.3 |
| adobe | commerce_b2b | 1.3.3 |
| adobe | commerce_b2b | 1.3.3 |
| adobe | commerce_b2b | 1.3.3 |
| adobe | commerce_b2b | 1.3.3 |
| adobe | commerce_b2b | 1.3.3 |
| adobe | commerce_b2b | 1.3.3 |
| adobe | commerce_b2b | 1.3.3 |
| adobe | commerce_b2b | 1.3.3 |
| adobe | commerce_b2b | 1.3.4 |
| adobe | commerce_b2b | 1.3.4 |
| adobe | commerce_b2b | 1.3.4 |
| adobe | commerce_b2b | 1.3.4 |
| adobe | commerce_b2b | 1.3.4 |
| adobe | commerce_b2b | 1.3.4 |
| adobe | commerce_b2b | 1.3.4 |
| adobe | commerce_b2b | 1.3.4 |
| adobe | commerce_b2b | 1.3.4 |
| adobe | commerce_b2b | 1.3.4 |
| adobe | commerce_b2b | 1.3.4 |
| adobe | commerce_b2b | 1.3.4 |
| adobe | commerce_b2b | 1.3.4 |
| adobe | commerce_b2b | 1.3.4 |
| adobe | commerce_b2b | 1.3.5 |
| adobe | commerce_b2b | 1.3.5 |
| adobe | commerce_b2b | 1.3.5 |
| adobe | commerce_b2b | 1.3.5 |
| adobe | commerce_b2b | 1.3.5 |
| adobe | commerce_b2b | 1.3.5 |
| adobe | commerce_b2b | 1.3.5 |
| adobe | commerce_b2b | 1.3.5 |
| adobe | commerce_b2b | 1.3.5 |
| adobe | commerce_b2b | 1.3.5 |
| adobe | commerce_b2b | 1.3.5 |
| adobe | commerce_b2b | 1.3.5 |
| adobe | commerce_b2b | 1.4.2 |
| adobe | commerce_b2b | 1.4.2 |
| adobe | commerce_b2b | 1.4.2 |
| adobe | commerce_b2b | 1.4.2 |
| adobe | commerce_b2b | 1.4.2 |
| adobe | commerce_b2b | 1.4.2 |
| adobe | commerce_b2b | 1.4.2 |
| adobe | commerce_b2b | 1.5.2 |
| adobe | commerce_b2b | 1.5.2 |
| adobe | commerce_b2b | 1.5.3 |
| adobe | commerce | to 2.4.4 (exc) |
| adobe | commerce | 2.4.4 |
| adobe | commerce | 2.4.4 |
| adobe | commerce | 2.4.4 |
| adobe | commerce | 2.4.4 |
| adobe | commerce | 2.4.4 |
| adobe | commerce | 2.4.4 |
| adobe | commerce | 2.4.4 |
| adobe | commerce | 2.4.4 |
| adobe | commerce | 2.4.4 |
| adobe | commerce | 2.4.4 |
| adobe | commerce | 2.4.4 |
| adobe | commerce | 2.4.4 |
| adobe | commerce | 2.4.4 |
| adobe | commerce | 2.4.4 |
| adobe | commerce | 2.4.4 |
| adobe | commerce | 2.4.5 |
| adobe | commerce | 2.4.5 |
| adobe | commerce | 2.4.5 |
| adobe | commerce | 2.4.5 |
| adobe | commerce | 2.4.5 |
| adobe | commerce | 2.4.5 |
| adobe | commerce | 2.4.5 |
| adobe | commerce | 2.4.5 |
| adobe | commerce | 2.4.5 |
| adobe | commerce | 2.4.5 |
| adobe | commerce | 2.4.5 |
| adobe | commerce | 2.4.5 |
| adobe | commerce | 2.4.5 |
| adobe | commerce | 2.4.5 |
| adobe | commerce | 2.4.6 |
| adobe | commerce | 2.4.6 |
| adobe | commerce | 2.4.6 |
| adobe | commerce | 2.4.6 |
| adobe | commerce | 2.4.6 |
| adobe | commerce | 2.4.6 |
| adobe | commerce | 2.4.6 |
Helpful Resources
Exploitability
CWE
KEV
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Path Traversal issue in Adobe Commerce versions up to 2.4.9-alpha1 and earlier. It allows an attacker to bypass security features by improperly limiting access to restricted directories, enabling them to modify limited data without requiring any user interaction.
How can this vulnerability impact me? :
The vulnerability could allow an attacker to modify restricted data within the affected Adobe Commerce system, potentially compromising data integrity. Since exploitation does not require user interaction, it can be triggered remotely, increasing the risk of unauthorized data modification.
Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70