How severe is GHSA-gm68-572p-q28r?

No CVSS score has been assigned to GHSA-gm68-572p-q28r yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-gm68-572p-q28r?

GHSA-gm68-572p-q28r affects the following packages: @vendure/admin-ui-plugin (npm). Ecosystems affected: npm.

How do I fix GHSA-gm68-572p-q28r?

Update @vendure/admin-ui-plugin to 2.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gm68-572p-q28r is resolved across your whole dependency graph.

How do I detect GHSA-gm68-572p-q28r in my npm dependencies?

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

How do I mitigate GHSA-gm68-572p-q28r if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-gm68-572p-q28r actively exploited in the wild?

No public exploit code has been indexed for GHSA-gm68-572p-q28r 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-gm68-572p-q28r published, and has it been updated?

GHSA-gm68-572p-q28r was published on July 6, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

@vendure/admin-ui-plugin authenticated Cross-site Scripting vulnerabilityGHSA-gm68-572p-q28r

Fix: vendure-ecommerce/vendure@0cdc92b

GHSA-gm68-572p-q28r is a remote code execution vulnerability in @vendure/admin-ui-plugin. A fix is available for @vendure/admin-ui-plugin — see the affected versions and patch details below.

Published

Jul 6, 2023

Updated

Jul 6, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jul 6, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

5other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@vendure/admin-ui-pluginnpm

4Kdownloads / week

Description

Impact

Vendure provides an authorization system with different levels of privileges. For example, an administrator cannot create another administrator.

In the admin UI, there are a couple of places with description inputs, such as inventory/collection catalog, shipping methods, promotions, and more.

While the WYSIWYG editor allows limited customization, altering the request data (not in the ui) saves and returns arbitrary HTML with no sanitization. Causing an XSS when viewing the page.

The impact of this XSS is privilege escalation. A user that can write any type of description can trigger the attack. Then any other user that visits the vulnerable page is prone to arbitrary Javascript code execution, giving the attacker ability to execute actions on behalf of this user.

Patches

in progress

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

References

Are there any links users can visit to find out more?

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@vendure/admin-ui-plugin`	all versions	2.0.3`npm install @vendure/admin-ui-plugin@2.0.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @vendure/admin-ui-plugin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @vendure/admin-ui-plugin to 2.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gm68-572p-q28r is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### Impact Vendure provides an authorization system with different levels of privileges. For example, an administrator cannot create another administrator. In the admin UI, there are a couple of places with description inputs, such as inventory/collection catalog, shipping methods, promotions, and more. While the WYSIWYG editor allows limited customization, altering the request data (not in the ui) saves and returns arbitrary HTML with no sanitization. Causing an XSS when viewing the page. The impact of this XSS is privilege escalation. A user that can write any type of description can trig

O3 Security · Impact-Aware SCA

Is GHSA-gm68-572p-q28r in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works