CVE-2024-34107: Adobe Commerce | Improper Access Control (CWE-284)
Noroxi assessment
Priority: Monitor (action score 39/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: 1.1% (FIRST EPSS); higher than 66.8% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: magento/community-edition (Packagist) 2.4.5-p8, 2.4.6-p6, 2.4.4-p9.
- Severity is disputed: the assigning authority (CNA) scores it 5.3, NVD 9.8.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to magento/community-edition (Packagist) 2.4.5-p8, 2.4.6-p6, 2.4.4-p9 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.7, 2.4.6-p5, 2.4.5-p7, 2.4.4-p8 and earlier are affected by an Improper Access Control vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to bypass security measures and view minor unauthorised information. Exploitation of this issue does not require user interaction.
- Published
- Jun 13, 2024
- Updated
- Jun 17, 2026
- EPSS
- 1.1% · 66th percentile
- CWE
- CWE-284
Report tools
Action score
39
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 9.8
- CNA · adobe
- 5.3
- 4.5 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 webhooks | cpe:2.3:a:adobe:commerce_webhooks |
| 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.4-p8affected · semver
Affected versions · NVD (13)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- adobe commerce2.3.7
- adobe commerce2.4.0
- adobe commerce2.4.1
- adobe commerce2.4.2
- adobe commerce2.4.3
- adobe commerce2.4.4
- adobe commerce2.4.5
- adobe commerce2.4.6
- adobe commerce webhooks1.2.0 and later · up to 1.4.0 inclusive
- adobe magento2.4.4
- adobe magento2.4.5
- adobe magento2.4.6
- adobe magento2.4.7
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.4 · up to and including 2.4.4 | — |
| 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-p8 | 2.4.5-p8 |
| 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-p6 | 2.4.6-p6 |
| Packagist | magento/community-edition | from 2.4.7 · up to and including 2.4.7 | — |
| Packagist | magento/community-edition | before 2.4.4-p9 | 2.4.4-p9 |
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-2024-34105Jun 13, 2024 · Stored Cross Site Scripting in Order Comment19Monitor
- ← EarlierCVE-2024-34106Jun 13, 2024 · Insecure Direct Object Reference - An attacker can able to erase the victim quote details21Monitor
- Later →CVE-2024-34108Jun 13, 2024 · Large attack surface through legit webhook usage in Adobe Commerce28Monitor
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-p9 | Package registry (OSV) |
| Packagist:magento/community-edition | 2.4.5-p8 | Package registry (OSV) |
| Packagist:magento/community-edition | 2.4.6-p6 | 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-24411243 days apartAdobe Commerce | Improper Access Control (CWE-284)32Monitor
- CVE-2025-43586362 days apartAdobe Commerce | Improper Access Control (CWE-284)32Monitor
- CVE-2024-45118119 days apartAdobe Commerce | Improper Access Control (CWE-284)26Monitor
- CVE-2025-24427243 days apartAdobe Commerce | Improper Access Control (CWE-284)26Monitor
- CVE-2024-45124119 days apartAdobe Commerce | Improper Access Control (CWE-284)21Monitor
- CVE-2025-27191299 days apartAdobe Commerce | Improper Access Control (CWE-284)21Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0708 · Jun 14, 2024(Adobe Commerce Güvenlik Bildirimi )
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.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-284 · Improper Access ControlCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
Attack patterns (CAPEC)
- Embedding Scripts within ScriptsCAPEC-19likelihood: High · High
- Malicious Logic InsertionCAPEC-441likelihood: Medium · High
- Modification of Windows Service ConfigurationCAPEC-478likelihood: Low · High
- Malicious Root CertificateCAPEC-479likelihood: Low · Low
- Intent SpoofCAPEC-502
- WebView ExposureCAPEC-503
- Data Injected During ConfigurationCAPEC-536likelihood: Low · High
- Incomplete Data Deletion in a Multi-Tenant EnvironmentCAPEC-546likelihood: Low · Medium
ATT&CK techniques
- RootkitT1014
- Obfuscated Files or Information: Embedded PayloadsT1027.009
- Boot or Logon Initialization ScriptsT1037
- Taint shared contentT1080
- Server Software Component: Terminal Services DLLT1505.005
- Pre-OS Boot:BootkitT1542.003
- Create or Modify System ProcessT1543
- Create or Modify System Process: Launch AgentT1543.001
- Create or Modify System Process:Windows ServiceT1543.003
- Create or Modify System Process: Launch DaemonT1543.004
- Event Triggered Execution:Change Default File AssociationT1546.001
- Event Triggered Execution:.bash_profile and .bashrcT1546.004
- Event Triggered Execution: Accessibility FeaturesT1546.008
- Event Triggered Execution: Installer PackagesT1546.016
- Boot or Logon Autostart ExecutionT1547
- Boot or Logon Autostart Execution:Kernel Modules and ExtensionsT1547.006
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.