How severe is GHSA-5qxq-vgmm-q39m?

GHSA-5qxq-vgmm-q39m has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-5qxq-vgmm-q39m?

GHSA-5qxq-vgmm-q39m affects the following packages: pimcore/pimcore (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-5qxq-vgmm-q39m?

Update pimcore/pimcore to 10.5.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5qxq-vgmm-q39m is resolved across your whole dependency graph.

How do I detect GHSA-5qxq-vgmm-q39m 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 GHSA-5qxq-vgmm-q39m if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is GHSA-5qxq-vgmm-q39m actively exploited in the wild?

No public exploit code has been indexed for GHSA-5qxq-vgmm-q39m 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 GHSA-5qxq-vgmm-q39m?

GHSA-5qxq-vgmm-q39m has an EPSS (Exploit Prediction Scoring System) score of 2.3%, placing it in the 83th 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 GHSA-5qxq-vgmm-q39m?

GHSA-5qxq-vgmm-q39m is classified as Code Injection (CWE-94). 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 GHSA-5qxq-vgmm-q39m published, and has it been updated?

GHSA-5qxq-vgmm-q39m was published on October 29, 2022 and was last updated on November 8, 2023. 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

CRITICAL severity

RCE vulnerability in Pimcore/Mail & Dynamic Text LayoutGHSA-5qxq-vgmm-q39m

CRITICALFix: pimcore/pimcore#13347

GHSA-5qxq-vgmm-q39m is a critical-severity (CVSS 9.8) Code Injection vulnerability in pimcore/pimcore. A fix is available for pimcore/pimcore — see the affected versions and patch details below.

Also known asCVE-2022-39365

Published

Oct 29, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs83th percentile — riskier than 83% 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

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

Impact

The user controlled twig templates rendering in Pimcore/Mail & ClassDefinition\Layout\Text is vulnerable to server-side template Injection RCE.

Patches

Update to version 10.5.9 or apply this patch manually https://github.com/pimcore/pimcore/pull/13347.patch

Workarounds

Apply https://github.com/pimcore/pimcore/pull/13347.patch manually.

References

Credits: @nth347 from Viettel Cyber Security

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 1 configurations

Application

pimcorepimcore

< 10.5.9

range

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 10.5.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5qxq-vgmm-q39m is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

### Impact The user controlled twig templates rendering in `Pimcore/Mail` & `ClassDefinition\Layout\Text` is vulnerable to server-side template Injection RCE. ### Patches Update to version 10.5.9 or apply this patch manually https://github.com/pimcore/pimcore/pull/13347.patch ### Workarounds Apply https://github.com/pimcore/pimcore/pull/13347.patch manually. ### References Credits: @nth347 from Viettel Cyber Security