CVE-2023-26366· NVD / CVE Program· CNA adobe

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

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.

MediumCVSS 6.8 · v3.1—No exploit Fix available

SSRF

Published: Oct 13, 2023
Updated: Jun 17, 2026
EPSS: 0.7% · 53th percentile
CWE: CWE-918

Follow this CVE

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 27 / 40 · 6.8 / 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: 6.8; 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.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

Vendor	Product	CPE
adobe	commerce	cpe:2.3:a:adobe:commerce
adobe	magento	cpe:2.3:a:adobe:magento

Affected versions

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 commerce2.4.7
adobe magento2.4.4
adobe magento2.4.5
adobe magento2.4.6
adobe magento2.4.7

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.7-beta1affected · semver

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-p1 · before 2.4.4-p6	2.4.4-p6
Packagist	magento/community-edition	from 2.4.5-p1 · before 2.4.5-p5	2.4.5-p5
Packagist	magento/community-edition	from 2.4.6-p1 · before 2.4.6-p3	2.4.6-p3
Packagist	magento/community-edition	from 2.4.7-beta1 · before 2.4.7-beta2	2.4.7-beta2
Packagist	magento/community-edition	all versions	—
Packagist	magento/project-community-edition	up to and including 2.0.2	—

Same product

adobe: all records

Other highest-scoring records for the same primary product.

CVE-2024-34102XXE can expose crypt key and other secrets granting full admin accessKEV
99Now
CVE-2022-24086Adobe Commerce checkout improper input validation leads to remote code executionKEV
99Now
CVE-2025-54236Adobe Commerce | Improper Input Validation (CWE-20)KEV
94Now
CVE-2026-71362Adobe Commerce | Incorrect Authorization (CWE-863)KEV
92Now
CVE-2026-75650Adobe Commerce | Improper Neutralization of Special Elements Used in a Template Engine (CWE-1336)KEV
71This week
CVE-2025-24434Adobe Commerce | Incorrect Authorization (CWE-863)
41Plan

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-p6	Package registry (OSV)
Packagist:magento/community-edition	2.4.5-p5	Package registry (OSV)
Packagist:magento/community-edition	2.4.6-p3	Package registry (OSV)
Packagist:magento/community-edition	2.4.7-beta2	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.

EPSS, last 120 days

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 researchers

Finders, 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-2024-34111244 days apartSSRF in service connector
35Monitor
CVE-2024-49521396 days apartAdobe Commerce | Server-Side Request Forgery (SSRF) (CWE-918)
30Monitor
CVE-2023-29291120 days apartServer Side Request Forgery (SSRF) in USPS carrier integration configuration
19Monitor
CVE-2023-29292120 days apartServer Side Request Forgery (SSRF) in FedEx carrier integration configuration
19Monitor
CVE-2024-45119363 days apartAdobe Commerce | Server-Side Request Forgery (SSRF) (CWE-918)
19Monitor

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