Summary
Reflected Cross-Site Scripting in redis-commander
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);}//
Impact
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
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.
Frequently Asked Questions
- What is GHSA-8C8C-4VFJ-RRPC? GHSA-8C8C-4VFJ-RRPC is a low-severity cross-site scripting (XSS) vulnerability in redis-commander (npm), affecting versions >= 0.0.0, < 0.5.0. It is fixed in 0.5.0. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- Which versions of redis-commander are affected by GHSA-8C8C-4VFJ-RRPC? redis-commander (npm) versions >= 0.0.0, < 0.5.0 is affected.
- Is there a fix for GHSA-8C8C-4VFJ-RRPC? Yes. GHSA-8C8C-4VFJ-RRPC is fixed in 0.5.0. Upgrade to this version or later.
- Is GHSA-8C8C-4VFJ-RRPC exploitable, and should I be worried? Whether GHSA-8C8C-4VFJ-RRPC is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-8C8C-4VFJ-RRPC is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-8C8C-4VFJ-RRPC? Upgrade
redis-commanderto 0.5.0 or later.