How severe is GHSA-jmh9-6rjq-gjh9?

No CVSS score has been assigned to GHSA-jmh9-6rjq-gjh9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jmh9-6rjq-gjh9?

GHSA-jmh9-6rjq-gjh9 affects the following packages: pimcore/admin-ui-classic-bundle (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-jmh9-6rjq-gjh9?

Update pimcore/admin-ui-classic-bundle to 1.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jmh9-6rjq-gjh9 is resolved across your whole dependency graph.

How do I detect GHSA-jmh9-6rjq-gjh9 in my Packagist dependencies?

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

How do I mitigate GHSA-jmh9-6rjq-gjh9 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.

How does O3 Security protect against GHSA-jmh9-6rjq-gjh9?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-jmh9-6rjq-gjh9 can be triaged on real exposure rather than presence alone.

Is GHSA-jmh9-6rjq-gjh9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-jmh9-6rjq-gjh9 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.

When was GHSA-jmh9-6rjq-gjh9 published, and has it been updated?

GHSA-jmh9-6rjq-gjh9 was published on June 5, 2024 and was last updated on December 2, 2024. 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

GHSA-jmh9-6rjq-gjh9 — pimcore/admin-ui-classic-…

GHSA-jmh9-6rjq-gjh9 is a security vulnerability in pimcore/admin-ui-classic-bundle. A fix is available for pimcore/admin-ui-classic-bundle — see the affected versions and patch details below.

Vulnerable embedded jQuery Version

Published

Jun 5, 2024

Updated

Dec 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘pimcore/admin-ui-classic-bundle

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

Summary

PIMCore uses the JavaScript library jQuery in version 3.4.1. This version is vulnerable to cross-site-scripting (XSS).

Details

In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing elements from untrusted sources - even after sanitizing it to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.

Publish Date: 2020-04-29

URL:= https://security.snyk.io/package/npm/jquery/3.4.1

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`pimcore/admin-ui-classic-bundle`	all versions	1.4.3`composer require pimcore/admin-ui-classic-bundle:^1.4.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pimcore/admin-ui-classic-bundle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pimcore/admin-ui-classic-bundle to 1.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jmh9-6rjq-gjh9 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-jmh9-6rjq-gjh9 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-jmh9-6rjq-gjh9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary PIMCore uses the JavaScript library jQuery in version 3.4.1. This version is vulnerable to cross-site-scripting (XSS). ### Details In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing elements from untrusted sources - even after sanitizing it to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0. Publish Date: 2020-04-29 URL:= https://security.snyk.io/package/npm/jquery/3.4.1

O3 Security · Impact-Aware SCA

Is GHSA-jmh9-6rjq-gjh9 in your dependencies?

O3 Security finds GHSA-jmh9-6rjq-gjh9 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works