CVE-2025-24421: Adobe Commerce | Incorrect Authorization (CWE-863)
Noroxi assessment
Priority: Monitor (action score 17/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.54% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: magento/community-edition (Packagist) 2.4.5-p11, 2.4.6-p9, 2.4.7-p4.
Low priority for now. Upgrade to magento/community-edition (Packagist) 2.4.5-p11, 2.4.6-p9, 2.4.7-p4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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 Incorrect Authorization vulnerability that could result in a security feature bypass. A low-privileged attacker could exploit this vulnerability to read select data. Exploitation of this issue does not require user interaction
- Published
- Feb 11, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.5% · 46th percentile
- CWE
- CWE-863
Report tools
Action score
17
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 4.3
- CNA · adobe
- 4.3
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| adobe | commerce | cpe:2.3:a:adobe:commerce |
| adobe | commerce b2b | cpe:2.3:a:adobe:commerce_b2b |
| adobe | magento | cpe:2.3:a:adobe:magento |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (adobe). Independent of NVD's CPE analysis and usually ahead of it.
Adobe Adobe Commerce
- up to and including 2.4.8-beta1affected · semver
Affected versions · NVD (18)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- adobe commercebefore 2.4.4
- adobe commerce2.4.4
- adobe commerce2.4.5
- adobe commerce2.4.6
- adobe commerce2.4.7
- adobe commerce2.4.8
- adobe commerce b2bbefore 1.3.3
- adobe commerce b2b1.3.3
- adobe commerce b2b1.3.4
- adobe commerce b2b1.3.5
- adobe commerce b2b1.4.2
- adobe commerce b2b1.5.0
- adobe magentobefore 2.4.4
- adobe magento2.4.4
- adobe magento2.4.5
- adobe magento2.4.6
- adobe magento2.4.7
- adobe magento2.4.8
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Packagist | magento/community-edition | from 2.4.5 · up to and including 2.4.5 | — |
| Packagist | magento/community-edition | from 2.4.5-p1 · before 2.4.5-p11 | 2.4.5-p11 |
| Packagist | magento/community-edition | from 2.4.6 · up to and including 2.4.6 | — |
| Packagist | magento/community-edition | from 2.4.6-p1 · before 2.4.6-p9 | 2.4.6-p9 |
| Packagist | magento/community-edition | from 2.4.7 · up to and including 2.4.7 | — |
| Packagist | magento/community-edition | from 2.4.7-beta1 · before 2.4.7-p4 | 2.4.7-p4 |
| Packagist | magento/community-edition | from 2.4.8-beta1 · up to and including 2.4.8-beta1 | — |
| Packagist | magento/community-edition | before 2.4.4-p12 | 2.4.4-p12 |
| Packagist | magento/project-community-edition | up to and including 2.0.2 | — |
Same product
adobe: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-75650Adobe Commerce | Improper Neutralization of Special Elements Used in a Template Engine (CWE-1336)KEV100Now
- CVE-2024-34102XXE can expose crypt key and other secrets granting full admin accessKEV99Now
- CVE-2022-24086Adobe Commerce checkout improper input validation leads to remote code executionKEV99Now
Published before and after this one in the same product
- ← EarlierCVE-2025-24416Feb 11, 2025 · Adobe Commerce | Cross-site Scripting (Stored XSS) (CWE-79)34Monitor
- ← EarlierCVE-2025-24417Feb 11, 2025 · Adobe Commerce | Cross-site Scripting (Stored XSS) (CWE-79)34Monitor
- Later →CVE-2025-24425Feb 11, 2025 · Adobe Commerce | Business Logic Errors (CWE-840)21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Packagist:magento/community-edition | 2.4.4-p12 | Package registry (OSV) |
| Packagist:magento/community-edition | 2.4.5-p11 | Package registry (OSV) |
| Packagist:magento/community-edition | 2.4.6-p9 | Package registry (OSV) |
| Packagist:magento/community-edition | 2.4.7-p4 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-244340 days apartAdobe Commerce | Incorrect Authorization (CWE-863)41Plan
- CVE-2023-38218487 days apartIncorrect Authorization - Customer account takeover35Monitor
- CVE-2026-47988518 days apartAdobe Commerce | Incorrect Authorization (CWE-863)34Monitor
- CVE-2025-244090 days apartAdobe Commerce | Incorrect Authorization (CWE-863)32Monitor
- CVE-2025-54263245 days apartAdobe Commerce | Incorrect Authorization (CWE-863)32Monitor
- CVE-2026-47984518 days apartAdobe Commerce | Incorrect Authorization (CWE-863)32Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.