How severe is CVE-2021-23340?

CVE-2021-23340 has a CVSS score of 7.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2021-23340?

CVE-2021-23340 affects the following packages: pimcore/pimcore (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2021-23340?

Update pimcore/pimcore to 6.8.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-23340 is resolved across your whole dependency graph.

How do I detect CVE-2021-23340 in my Packagist dependencies?

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

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

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2021-23340 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2021-23340, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2021-23340?

CVE-2021-23340 has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 70th 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-2021-23340?

CVE-2021-23340 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2021-23340 published, and has it been updated?

CVE-2021-23340 was published on February 18, 2021 and was last updated on August 7, 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

HIGH severity

CVE-2021-23340 — pimcore

HIGHFix: pimcore/pimcore@1786bdd

CVE-2021-23340 is a high-severity (CVSS 7.1) Path Traversal vulnerability in pimcore/pimcore. 1 public exploit reference exists, so weaponization risk is real. A fix is available for pimcore/pimcore — see the affected versions and patch details below.

Path traversal in pimcore/pimcore

Also known asGHSA-h7f9-cvh5-qw7fSNYK-PHP-PIMCOREPIMCORE-1070132

Published

Feb 18, 2021

Updated

Aug 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs70th percentile — riskier than 70% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2021-23340 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

🐘pimcore/pimcore

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

This affects the package pimcore/pimcore before 6.8.8. A Local FIle Inclusion vulnerability exists in the downloadCsvAction function of the CustomReportController class (bundles/AdminBundle/Controller/Reports/CustomReportController.php). An authenticated user can reach this function with a GET request at the following endpoint: /admin/reports/custom-report/download-csv?exportFile=&91;filename]. Since exportFile variable is not sanitized, an attacker can exploit a local file inclusion vulnerability.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`pimcore/pimcore`	all versions	6.8.8`composer require pimcore/pimcore:^6.8.8`

Affected Products

1 product · 1 configurations

Application

pimcorepimcore

< 6.8.8

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

This affects the package pimcore/pimcore before 6.8.8. A Local FIle Incl…

snyk.ioNVDFeb 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pimcore/pimcore, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pimcore/pimcore to 6.8.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-23340 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2021-23340 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

Low

Availability

None

Raw vector

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

CWE Classification

CWE-22Path Traversal

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

pimcore

5.0/10

Maintained10/10

Code-Review3/10

Branch-Protection1/10

Assessed Oct 5, 2026

Timeline

Disclosed

Feb 18, 2021

First exploit

Feb 25, 2021

7 days after disclosure — rapid exploitation

Last updated

Aug 7, 2026

Identifiers

CVE-2021-23340

GHSA-h7f9-cvh5-qw7f

SNYK-PHP-PIMCOREPIMCORE-1070132

References

Advisorygithub.com Advisorynvd.nist.gov Fixgithub.com Fixsnyk.io

Related vulnerabilities

This CVE is high severity; 7 of 8 other CVEs affecting pimcore/pimcore are rated as high or higher (top: critical).

CVE-2026-55416CVE-2026-55634CVE-2026-55220CVE-2026-55072CVE-2026-11407CVE-2026-5394CVE-2026-44739CVE-2026-45703

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedAug 7, 2026