CVE-2025-24418 Details
Description
Adobe Commerce versions 2.4.8-beta1, 2.4.7-p3, 2.4.6-p8, 2.4.5-p10, 2.4.4-p11 and earlier are affected by an Improper Authorization vulnerability that could result in Privilege escalation. A low-privileged attacker could leverage this vulnerability to bypass security measures and gain unauthorized access. Exploitation of this issue does not require user interaction.
A vulnerability allowing improper authorization has been identified in Adobe Commerce versions 2.4.8-beta1, 2.4.7-p3, 2.4.6-p8, 2.4.5-p10, 2.4.4-p11 and earlier. This vulnerability could lead to privilege escalation, as a low-privileged attacker might exploit it to bypass security measures and gain unauthorized access. Notably, exploitation of this vulnerability does not require user interaction.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Feb 14, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://helpx.adobe.com/security/products/magento/apsb25-08.html | [email protected] | Vendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
| CWE-285 | Improper Authorization | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| adobe commerce b2b | < 1.3.3 1.3.3 - 1.3.3 p10 1.3.3 p11 1.3.4 - 1.3.4 p10 1.3.4 p9 1.3.5 - 1.3.5 p7 1.3.5 p8 1.4.2 - 1.4.2 p1 1.4.2 p2 1.4.2 p3 1.5.0 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Mar 5, 2025 | Initial Analysis | [email protected] |
| Feb 27, 2025 | CVE Modified | [email protected] |
| Feb 11, 2025 | New CVE Received | [email protected] |