Adobe Commerce | Incorrect Authorization (CWE-863)
Noroxi assessment
Priority: Monitor (action score 23/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.70% (FIRST EPSS); higher than 52.9% 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. Special conditions such as timing or configuration are required.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
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 is affected by an Incorrect Authorization vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to bypass security measures and gain unauthorized read access. Exploit depends on conditions beyond the attacker's control. Exploitation of this issue does not require user interaction.
- Published
- Jul 14, 2026
- Updated
- Aug 27, 2026
- EPSS
- 0.7% · 52th percentile
- CWE
- CWE-863
Report tools
Action score
23
Monitor
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · adobe
- 5.9
- NVD has not scored this yet; the score shown is the CNA’s.
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
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 |
| adobe | i\/o events | cpe:2.3:a:adobe:i\/o_events |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- adobe commerce2.4.4
- adobe commerce2.4.5
- adobe commerce2.4.6
- adobe commerce2.4.7
- adobe commerce2.4.8
- adobe commerce2.4.9
- adobe commerce b2b1.3.3
- adobe commerce b2b1.3.4
- adobe commerce b2b1.4.2
- adobe commerce b2b1.5.2
- adobe commerce b2b1.5.3
- adobe i/o events1.6.0 and later · before 1.21.0
- adobe magento2.4.6
- adobe magento2.4.7
- adobe magento2.4.8
- adobe magento2.4.9
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
- 2.4.9-2026-jul, 2.4.8-2026-jul, 2.4.7-2026-jul, 2.4.6-2026-jul, 2.4.5-2026-jul, 2.4.4-2026-julnot affected
- up to and including 2.4.9, 2.4.8-p5, 2.4.7-p10, 2.4.6-p15, 2.4.5-p17, 2.4.4-p18affected
Adobe Adobe Commerce B2B
- 1.5.3-2026-jul, 1.5.2-2026-jul, 1.4.2-2026-jul, 1.3.4-2026-jul, 1.3.3-2026-julnot affected
- up to and including 1.5.3, 1.5.2-p5, 1.4.2-p10, 1.3.4-p17, 1.3.3-p18affected
Adobe Adobe Commerce Events
- 1.21.0not affected
- up to and including 1.20.0affected · semver
Adobe Magento Open Source
- 2.4.9-2026-jul, 2.4.8-2026-jul, 2.4.7-2026-jul, 2.4.6-2026-julnot affected
- up to and including 2.4.9, 2.4.8-p5, 2.4.7-p10, 2.4.6-p15affected
Same product
adobe: all recordsOther highest-scoring records for the same primary product.
- 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
- CVE-2025-54236Adobe Commerce | Improper Input Validation (CWE-20)KEV94Now
Published before and after this one in the same product
- ← EarlierCVE-2026-47995Jul 14, 2026 · Adobe Commerce | Cross-site Scripting (Stored XSS) (CWE-79)32Monitor
- ← EarlierCVE-2026-47996Jul 14, 2026 · Adobe Commerce | Incorrect Authorization (CWE-863)27Monitor
- Later →CVE-2026-47998Jul 14, 2026 · Adobe Commerce | Incorrect Authorization (CWE-863)23Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-7136228 days apartAdobe Commerce | Incorrect Authorization (CWE-863)KEV92Now
- CVE-2025-24434518 days apartAdobe Commerce | Incorrect Authorization (CWE-863)41Plan
- CVE-2026-479880 days apartAdobe Commerce | Incorrect Authorization (CWE-863)34Monitor
- CVE-2026-7710956 days apartAdobe Commerce | Incorrect Authorization (CWE-863)34Monitor
- CVE-2026-7711156 days apartAdobe Commerce | Incorrect Authorization (CWE-863)34Monitor
- CVE-2026-7777456 days apartAdobe Commerce | Incorrect Authorization (CWE-863)34Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-secondary
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
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.