CVE-2025-54267 — project-community-edition
MEDIUMCVE-2025-54267 is a medium-severity (CVSS 6.5) CWE-863 vulnerability in magento/project-community-edition. A fix is available for magento/project-community-edition — see the affected versions and patch details below.
Adobe Commerce | Incorrect Authorization (CWE-863)
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-54267.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
magento/project-community-edition🐘magento/community-edition🐘magento/community-edition🐘magento/community-edition🐘magento/community-edition🐘magento/community-edition🐘magento/community-edition🐘magento/community-editionReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
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 Incorrect Authorization vulnerability. A low-privileged attacker could leverage this vulnerability to bypass security measures and gain unauthorized access to elevated privileges that increase integrity impact to high. Exploitation of this issue does not require user interaction.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | magento/project-community-edition | all versions | No fix |
| 🐘Packagist | magento/community-edition | ≥ 2.4.9-alpha1&&< 2.4.9-alpha3 | 2.4.9-alpha3composer require magento/community-edition:^2.4.9-alpha3 |
| 🐘Packagist | magento/community-edition | ≥ 2.4.8-beta1&&< 2.4.8-p3 | 2.4.8-p3composer require magento/community-edition:^2.4.8-p3 |
| 🐘Packagist | magento/community-edition | ≥ 2.4.7-beta1&&< 2.4.7-p8 | 2.4.7-p8composer require magento/community-edition:^2.4.7-p8 |
| 🐘Packagist | magento/community-edition | all versions | 2.4.6-p13composer require magento/community-edition:^2.4.6-p13 |
| 🐘Packagist | magento/community-edition | all versions | No fix |
Affected Products
commerceadobecommerce b2badobemagentoadobeDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for magento/project-community-edition, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
A fix is available for CVE-2025-54267; check the affected-versions list above or the advisory for the patched release of magento/project-community-edition, then make sure no transitive dependency still pins the vulnerable range.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2025-54267 in your dependencies?
Find it across Packagist, including transitive dependencies.