Cross Site Scripting (XSS) in SimikiGHSA-fqr5-qphf-vfr8
MEDIUMGHSA-fqr5-qphf-vfr8 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in simiki. 1 public exploit reference exists, so weaponization risk is real. A fix is available for simiki — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-fqr5-qphf-vfr8 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
simikiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Cross Site Scripting (XSS) in Simiki v1.6.2.1 and prior allows remote attackers to execute arbitrary code via line 54 of the component 'simiki/blob/master/simiki/generators.py'.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | simiki | all versions | 1.6.2.2pip install --upgrade 'simiki==1.6.2.2' |
Affected Products
simikisimiki_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for simiki, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update simiki to 1.6.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fqr5-qphf-vfr8 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
Is GHSA-fqr5-qphf-vfr8 in your dependencies?
Find it across PyPI, including transitive dependencies.