CVE-2016-10547 — nunjucks
MEDIUMCVE-2016-10547 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in nunjucks. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for nunjucks — see the affected versions and patch details below.
Cross-Site Scripting in nunjucks
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.
nunjucksnpmDescription
Affected versions of nunjucks do not properly escape specially structured user input in template vars when in auto-escape mode, resulting in a cross-site scripting vulnerability.
Proof of Concept
By using an array for the keys in a template var, escaping is bypassed.
name[]=<script>alert(1)</script>
A full PoC is available in the references section.
Recommendation
Update to version 2.4.3 or later.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | nunjucks | all versions | 2.4.3npm install nunjucks@2.4.3 |
Affected Products
nunjucksmozillaResearch 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 nunjucks, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update nunjucks to 2.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-10547 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-2016-10547 in your dependencies?
Find it across npm, including transitive dependencies.