CVE-2022-1291 is a high-severity (CVSS 7.6) Cross-site Scripting (XSS) vulnerability in tableexport.jquery.plugin. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for tableexport.jquery.plugin — see the affected versions and patch details below.
XSS vulnerability with default `onCellHtmlData` function in hhurz/tableexport.jquery.plugin
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
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.
tableexport.jquery.pluginnpmDescription
There is a cross-site scripting vulnerability with default onCellHtmlData function in GitHub repository hhurz/tableexport.jquery.plugin prior to 1.25.0. This can result in transmitting cookies to third-party servers and/or sending data from secure sessions to third-party servers.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | tableexport.jquery.plugin | all versions | 1.25.0npm install tableexport.jquery.plugin@1.25.0 |
Affected Products
tableexport.jquery.plugintableexport.jquery.plugin_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 tableexport.jquery.plugin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update tableexport.jquery.plugin to 1.25.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-1291 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 CVE-2022-1291 in your dependencies?
Find it across npm, including transitive dependencies.