NVD / CVE Program· CNA GitHub_M

CVE-2023-30852: Pimcore Arbitrary File Read in Admin JS CSS files

Noroxi assessment

Priority: Monitor (action score 19/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1% (FIRST EPSS); higher than 62.7% of all records.
Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: pimcore/pimcore (Packagist) 10.5.21.

Low priority for now. Upgrade to pimcore/pimcore (Packagist) 10.5.21 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Pimcore is an open source data and experience management platform. Prior to version 10.5.21, the `/admin/misc/script-proxy` API endpoint that is accessible by an authenticated administrator user is vulnerable to arbitrary JavaScript and CSS file read via the `scriptPath` and `scripts` parameters. The `scriptPath` parameter is not sanitized properly and is vulnerable to path traversal attack. Any JavaScript/CSS file from the application server can be read by specifying sufficient number of `../` patterns to go out from the application webroot followed by path of the folder where the file is located in the "scriptPath" parameter and the file name in the "scripts" parameter. The JavaScript file is successfully read only if the web application has read access to it. Users should update to version 10.5.21 to receive a patch or, as a workaround, apply the patch manual.

MediumCVSS 4.9 · v3.1—No exploit Fix available

Path traversal

GHSA-j5c3-r84f-9596

Published: Apr 27, 2023
Updated: Jun 17, 2026
EPSS: 1.0% · 62th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 19 / 40 · 4.9 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.0%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 4.9
CNA · GitHub_M: 4.4; 0.5 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
pimcore	pimcore	cpe:2.3:a:pimcore:pimcore

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

pimcore pimcorebefore 10.5.21

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

pimcore pimcore
- < 10.5.21affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Packagist	pimcore/pimcore	before 10.5.21	10.5.21

Same product

pimcore: all records

Other highest-scoring records for the same primary product.

CVE-2019-10867An issue was discovered in Pimcore before 5.7.1.
56Plan
CVE-2023-1578SQL Injection in pimcore/pimcore
54Plan
CVE-2022-1429SQL injection in GridHelperService.php in pimcore/pimcore
49Plan

Published before and after this one in the same product

← EarlierCVE-2023-30849Apr 27, 2023 · Pimcore vulnerable to SQL Injection in Translation Export API
35Monitor
← EarlierCVE-2023-30850Apr 27, 2023 · Pimcore SQL Injection Vulnerability in Admin Translations API
35Monitor
Later →CVE-2023-2361Apr 28, 2023 · Cross-site Scripting (XSS) - Stored in pimcore/pimcore
21Monitor

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:pimcore/pimcore	10.5.21	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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

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.

No nightly-computed relations.

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

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
Administrator privileges are required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: High
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

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

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:47 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/pimcore/pimcore/commit/498cadec2292f7842fb10612068ac78496e884b4.patch

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records