How severe is GHSA-c53x-wwx2-pg96?

GHSA-c53x-wwx2-pg96 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-c53x-wwx2-pg96?

GHSA-c53x-wwx2-pg96 affects the following packages: @berslucas/liljs (npm). Ecosystems affected: npm.

How do I fix GHSA-c53x-wwx2-pg96?

Update @berslucas/liljs to 1.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c53x-wwx2-pg96 is resolved across your whole dependency graph.

How do I detect GHSA-c53x-wwx2-pg96 in my npm dependencies?

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

How do I mitigate GHSA-c53x-wwx2-pg96 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-c53x-wwx2-pg96 actively exploited in the wild?

No public exploit code has been indexed for GHSA-c53x-wwx2-pg96 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-c53x-wwx2-pg96 published, and has it been updated?

GHSA-c53x-wwx2-pg96 was published on September 3, 2020 and was last updated on September 28, 2021. 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

MEDIUM severity

Cross-Site Scripting in @berslucas/liljsGHSA-c53x-wwx2-pg96

MEDIUMFix: bersLucas/liljs#7

GHSA-c53x-wwx2-pg96 is a medium-severity (CVSS 6.5) vulnerability in @berslucas/liljs. A fix is available for @berslucas/liljs — see the affected versions and patch details below.

Published

Sep 3, 2020

Updated

Sep 28, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 28, 2021 · 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.

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

@berslucas/liljsnpm

35downloads / week

Description

Versions of @berslucas/liljs prior to 1.0.2 are vulnerable to Cross-Site Scripting (XSS). The package uses the unsafe innerHTML function without sanitizing input, which may allow attackers to execute arbitrary JavaScript on the victim's browser.

Recommendation

Upgrade to version 1.0.2 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@berslucas/liljs`	all versions	1.0.2`npm install @berslucas/liljs@1.0.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @berslucas/liljs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @berslucas/liljs to 1.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c53x-wwx2-pg96 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

Versions of `@berslucas/liljs` prior to 1.0.2 are vulnerable to Cross-Site Scripting (XSS). The package uses the unsafe `innerHTML` function without sanitizing input, which may allow attackers to execute arbitrary JavaScript on the victim's browser. ## Recommendation Upgrade to version 1.0.2 or later.

O3 Security · Impact-Aware SCA

Is GHSA-c53x-wwx2-pg96 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works