How severe is GHSA-8c8c-4vfj-rrpc?

No CVSS score has been assigned to GHSA-8c8c-4vfj-rrpc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8c8c-4vfj-rrpc?

GHSA-8c8c-4vfj-rrpc affects the following packages: redis-commander (npm). Ecosystems affected: npm.

How do I fix GHSA-8c8c-4vfj-rrpc?

Update redis-commander to 0.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8c8c-4vfj-rrpc is resolved across your whole dependency graph.

How do I detect GHSA-8c8c-4vfj-rrpc in my npm dependencies?

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

How do I mitigate GHSA-8c8c-4vfj-rrpc 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-8c8c-4vfj-rrpc actively exploited in the wild?

No public exploit code has been indexed for GHSA-8c8c-4vfj-rrpc 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-8c8c-4vfj-rrpc published, and has it been updated?

GHSA-8c8c-4vfj-rrpc was published on September 1, 2020 and was last updated on March 4, 2022. 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

Reflected Cross-Site Scripting in redis-commanderGHSA-8c8c-4vfj-rrpc

Fix: joeferner/redis-commander@1a483eb

GHSA-8c8c-4vfj-rrpc is a security vulnerability in redis-commander. A fix is available for redis-commander — see the affected versions and patch details below.

Published

Sep 1, 2020

Updated

Mar 4, 2022

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 4, 2022 · 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.

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

redis-commandernpm

5Kdownloads / week

Description

Affected versions of redis-commander contain a cross-site scripting vulnerability in the highlighterId paramter of the clipboard.swf component on hosts serving Redis Commander.

Mitigating factors: Flash must be installed / enabled for this to work. The below proof of concept was verified to work using Firefox 57.0 on Windows 10 by manually installing the Flash NPAPI Windows plugin

Proof of concept

http://instance/jstree/_docs/syntax/clipboard.swf?highlighterId=\%22))}%20catch(e)%20{alert(document.domain);}//

Recommendation

No direct patch for this vulnerability is currently available.

At this time, the best mitigation is to use an alternative, functionally equivalent package, or to use extreme caution when using redis-commander, ensuring that redis-commmander is the only web page you have open, and avoiding clicking on any links.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`redis-commander`	≥ 0.0.0&&< 0.5.0	0.5.0`npm install redis-commander@0.5.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for redis-commander, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update redis-commander to 0.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8c8c-4vfj-rrpc 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

Affected versions of `redis-commander` contain a cross-site scripting vulnerability in the `highlighterId` paramter of the clipboard.swf component on hosts serving Redis Commander. Mitigating factors: Flash must be installed / enabled for this to work. The below proof of concept was verified to work using Firefox 57.0 on Windows 10 by manually installing the [Flash NPAPI Windows plugin](https://get.adobe.com/flashplayer/otherversions/) ## Proof of concept ``` http://instance/jstree/_docs/syntax/clipboard.swf?highlighterId=\%22))}%20catch(e)%20{alert(document.domain);}// ``` ## Recommendat

O3 Security · Impact-Aware SCA

Is GHSA-8c8c-4vfj-rrpc in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works