GHSA-jg4p-g6xj-4qmf is a high-severity (CVSS 8.2) Cross-site Scripting (XSS) vulnerability in defuddle. A fix is available for defuddle — see the affected versions and patch details below.
Defuddle vulnerable to XSS via unescaped attribute interpolation in site extractors
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-jg4p-g6xj-4qmf.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-jg4p-g6xj-4qmf by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 382,795 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
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.
defuddlenpmDescription
Summary
An Improper Neutralization of Input During Web Page Generation issue in the site extractor component allows an attacker-controlled attribute value to be injected into output HTML without escaping. An attacker who crafts a malicious HTML page or controls content on a matching domain can execute arbitrary scripts when a victim processes the page, resulting in Cross-Site Scripting (XSS). This affects defuddle through 0.19.0 and has been patched in version 0.19.1.
Impact
This vulnerability allows for Cross-Site Scripting (XSS) execution without needing to compromise external websites. Affected consumers include:
- Obsidian Web Clipper,
- web services serving the parsed output directly as HTML, and
- any downstream application rendering the unsanitized HTML results
Patch
This issue has been patched in defuddle version 0.19.1. Users are encouraged to update to the latest release.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | defuddle | all versions | 0.19.1npm install defuddle@0.19.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for defuddle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update defuddle to 0.19.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jg4p-g6xj-4qmf 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-jg4p-g6xj-4qmf in your dependencies?
Find it across npm, including transitive dependencies.