Loading vulnerability…
CVE-2025-24408 is an information exposure vulnerability affecting Adobe Commerce and Magento Open Source. Affected versions include Adobe Commerce 2.4.8-beta1, 2.4.7-p3, 2.4.6-p8, 2.4.5-p10, 2.4.4-p11 and earlier corresponding branches, with fixed releases beginning at 2.4.8-beta2, 2.4.7-p4, 2.4.6-p9, 2.4.5-p11, and 2.4.4-p12. The issue is classified as CWE-200 and has been described as exploitable through path traversal and exposure of publicly available system information, enabling a low-privileged attacker to obtain unauthorized access to sensitive information. The vulnerability does not require user interaction for exploitation and may facilitate privilege escalation.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Adobe Commerce path traversal-related vulnerability that can be exploited without user interaction for privilege escalation.
A critical information exposure vulnerability in Adobe Commerce and Magento Open Source that could lead to privilege escalation with authentication and admin privileges.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.