GHSA-8c6x-g4fw-8rf4 is a medium-severity (CVSS 5.4) vulnerability in whatsapp-chat-exporter. A fix is available for whatsapp-chat-exporter — see the affected versions and patch details below.
Whatsapp-Chat-Exporter has Cross-Site Scripting vulnerability in HTML output of chats.
Real-World Exposure
whatsapp-chat-exporterReal-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
Impact
A Cross-Site Scripting (XSS) vulnerability was found in the HTML output of chats. XSS is intended to be mitigated by Jinja's escape function. However, autoescape=True was missing when setting the environment. Although the actual impact is low, considering the HTML file is being viewed offline, an adversary may still be able to inject malicious payloads into the chat through WhatsApp. All users are affected.
Patches
The vulnerability is patched in 0.9.5. All users are strongly advised to update the exporter to the latest version.
Workarounds
No workaround is available. Please update the exporter to the latest version.
References
https://github.com/KnugiHK/WhatsApp-Chat-Exporter/commit/bfdc68cd6ad53ceecf132773f9aaba50dd80fe79 https://owasp.org/www-community/attacks/xss/
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | whatsapp-chat-exporter | all versions | 0.9.5pip install --upgrade 'whatsapp-chat-exporter==0.9.5' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for whatsapp-chat-exporter, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update whatsapp-chat-exporter to 0.9.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8c6x-g4fw-8rf4 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-8c6x-g4fw-8rf4 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-8c6x-g4fw-8rf4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-8c6x-g4fw-8rf4 in your dependencies?
O3 Security finds GHSA-8c6x-g4fw-8rf4 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.