How severe is CVE-2023-26367?

CVE-2023-26367 has a CVSS score of 4.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2023-26367?

CVE-2023-26367 affects the following packages: magento/community-edition (Packagist), magento/community-edition (Packagist), magento/community-edition (Packagist), magento/community-edition (Packagist), magento/community-edition (Packagist), magento/community-edition (Packagist), magento/community-edition (Packagist), magento/community-edition (Packagist), and 1 more. Ecosystems affected: Packagist.

How do I fix CVE-2023-26367?

Update magento/community-edition to 2.4.7-beta2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-26367 is resolved across your whole dependency graph.

How do I detect CVE-2023-26367 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for magento/community-edition, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-26367 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2023-26367 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-26367 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2023-26367?

CVE-2023-26367 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 57th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-26367?

CVE-2023-26367 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2023-26367 published, and has it been updated?

CVE-2023-26367 was published on October 13, 2023 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

CVE-2023-26367 — community-edition

MEDIUM

CVE-2023-26367 is a medium-severity (CVSS 4.9) Improper Input Validation vulnerability in magento/community-edition. A fix is available for magento/community-edition — see the affected versions and patch details below.

Error based file extraction via PHP filter chains during product bulk import logic

Also known asGHSA-9mx6-4gg4-85xj

Published

Oct 13, 2023

Updated

Oct 28, 2026

Affected

9 pkgs

Patched

4 / 9

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-26367.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs57th percentile — riskier than 57% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

9 pkgs affected

🐘magento/community-edition🐘magento/community-edition🐘magento/community-edition🐘magento/community-edition🐘magento/community-edition🐘magento/community-edition🐘magento/community-edition🐘magento/community-edition+1 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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 an Improper Input Validation vulnerability that could lead to arbitrary file system read by an admin-privilege authenticated attacker. Exploitation of this issue does not require user interaction.

Affected Packages

9 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`magento/community-edition`	≥ 2.4.7-beta1&&< 2.4.7-beta2	2.4.7-beta2`composer require magento/community-edition:^2.4.7-beta2`
🐘Packagist	`magento/community-edition`	all versions	No fix
🐘Packagist	`magento/community-edition`	all versions	No fix
🐘Packagist	`magento/community-edition`	all versions	No fix
🐘Packagist	`magento/community-edition`	all versions	No fix
🐘Packagist	`magento/community-edition`	≥ 2.4.6-p1&&< 2.4.6-p3	2.4.6-p3`composer require magento/community-edition:^2.4.6-p3`

Affected Products

2 products · 58 configurations

Application

commerceadobe

9 versions

2.3.72.4.02.4.12.4.22.4.32.4.42.4.52.4.62.4.7

Application

magentoadobe

4 versions

2.4.42.4.52.4.62.4.7

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for magento/community-edition, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update magento/community-edition to 2.4.7-beta2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-26367 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2023-26367 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

4.9/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

CWE Classification

CWE-20Improper Input Validation

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Oct 13, 2023

Last updated

Oct 28, 2026

Identifiers

CVE-2023-26367

GHSA-9mx6-4gg4-85xj

References

Advisorygithub.com · CVE 2023 26367.json Advisoryhelpx.adobe.com · apsb23 50 Advisorynvd.nist.gov · CVE 2023 26367 Packagegithub.com · magento2

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting magento/community-edition are rated as high or higher (top: critical).

CVE-2025-54264CVE-2025-54263CVE-2025-54266CVE-2025-54267CVE-2025-54265CVE-2025-54236CVE-2025-49555CVE-2025-49556

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2023-26367 — community-edition

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2023-26367 in your dependencies?