Skip to content
Fencer Intel
medium 6.8

CVE-2023-26366 json

Validate Your Inputs | Server-Side Request Forgery (SSRF) (CWE-918)

published 3y ago modified 4mo ago also GHSA-8jxc-5f94-22vh , EUVD-2023-30186

cvss
6.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 59%
public exploits
0
none known

Summary

Adobe Commerce versions 2.4.7-beta1 (and earlier), 2.4.6-p2 (and earlier), 2.4.5-p4 (and earlier) and 2.4.4-p5 (and earlier) are affected by a Server-Side Request Forgery (SSRF) vulnerability that could lead to arbitrary file system read. A high-privileged authenticated attacker can force the application to make arbitrary requests via injection of arbitrary URLs. Exploitation of this issue does not require user interaction, scope is changed due to the fact that an attacker can enforce file read outside the application's path boundary.

Patch / fix

  • packagist magento/community-edition 2.4.4-p6, 2.4.5-p5, 2.4.6-p3, 2.4.7-beta2

Is CVE-2023-26366 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.86% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-15).

CVSS scores

assigned by version score vector
CNA 3.1 6.8 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
GitHub 3.1 6.8 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
packagist magento/community-edition
>=2.4.7-beta1, <2.4.7-beta2
1 listed version
>=2.4.6-p1, <2.4.6-p3
>=2.4.5-p1, <2.4.5-p5
>=2.4.4-p1, <2.4.4-p6
2.4.7-beta2
2.4.6-p3
2.4.5-p5
2.4.4-p6
packagist magento/project-community-edition
<=2.0.2
no fix listed

Affected products

  • Adobe Adobe Commerce

Classification

Weakness
  • CWE-918 Server-Side Request Forgery

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.