CVE-2023-26366
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAdobe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAdobe Commerce contains a Server-Side Request Forgery (SSRF) vulnerability in 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. A high-privileged authenticated attacker can inject arbitrary URLs to force the application to make requests to attacker-controlled endpoints, leading to arbitrary file system read outside the application's path boundary. No user interaction is required for exploitation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.3.7= 2.4.0= 2.4.1= 2.4.2= 2.4.3= 2.4.4= 2.4.5= 2.4.6= 2.4.7= 2.4.4= 2.4.5= 2.4.6= 2.4.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Adobe Commerce or Magento versionRun the command 'php bin/magento --version' from the web root directory, or check the 'composer.json' file for the 'version' field, or log into the admin panel and navigate to System > Tools > Web Setup Wizard to view the installed version.Affected if The installed version is 2.4.4, 2.4.5, 2.4.6, or 2.4.7 (including beta/alpha versions) and is not patched to 2.4.4-p6, 2.4.5-p5, 2.4.6-p3, or 2.4.7 or later.
-
Verify administrative access exposureCheck if the admin panel (typically at /admin or /backend) is accessible from the internet or untrusted networks. Review firewall rules, web server configuration, and network ACLs for the admin URL.Affected if The admin panel is accessible from untrusted networks without IP restriction or VPN, allowing high-privileged authenticated attackers to reach the vulnerable endpoint.
-
Review outbound HTTP request logsInspect web server access logs and application logs for suspicious outbound requests from the server. Look for requests to unusual or external domains originating from the application, particularly from IP addresses associated with the web server.Affected if The logs show outbound requests from the application to attacker-controlled or unexpected external URLs that were not initiated by legitimate administrative actions.
-
Check for unauthorized module installationsReview the 'app/code' and 'vendor' directories for any unknown or recently added modules that handle URL fetching or HTTP requests, particularly those that may have been injected by an attacker.Affected if Unknown modules exist that perform URL handling or HTTP requests and were not installed by trusted administrators.
You are affected if your installed Adobe Commerce/Magento version falls within the affected ranges (2.4.7-beta1 and earlier, 2.4.6-p2 and earlier, 2.4.5-p4 and earlier, 2.4.4-p5 and earlier) and your admin panel is accessible to a high-privileged authenticated attacker who could exploit the SSRF to make arbitrary requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply the available security patch or upgrade to a patched version of Adobe Commerce (2.4.4-p6, 2.4.5-p5, 2.4.6-p3, or 2.4.7 or later). Restrict administrative access to trusted personnel and implement network segmentation to limit the impact of SSRF attacks.
For 2.4.4.x: upgrade to 2.4.4-p5+ | For 2.4.5.x: upgrade to 2.4.5-p4+ | For 2.4.6.x: upgrade to 2.4.6-p2+ | For 2.4.7.x: upgrade to 2.4.7-p1+
- 1. Identify your current Adobe Commerce/Magento version using bin/magento --version or checking composer.json
- 2. For Magento 2.4.4: Upgrade to version 2.4.4-p5 or later (composer require magento/product-community-edition=2.4.4-p5 --no-update && composer update)
- 3. For Magento 2.4.5: Upgrade to version 2.4.5-p4 or later (composer require magento/product-community-edition=2.4.5-p4 --no-update && composer update)
- 4. For Magento 2.4.6: Upgrade to version 2.4.6-p2 or later (composer require magento/product-community-edition=2.4.6-p2 --no-update && composer update)
- 5. For Magento 2.4.7: Upgrade to version 2.4.7-p1 or later (composer require magento/product-community-edition=2.4.7-p1 --no-update && composer update)
- 6. Run composer update to apply changes
- 7. Clear the cache: rm -rf var/cache generated/code var/page_cache
- 8. Run setup upgrade: bin/magento setup:upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-26366 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-26366 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data