{"id":"CVE-2022-0239","url":"https://www.cyber-defence.io/tools/cve/CVE-2022-0239","generatedAt":"2026-10-27T18:40:15.540Z","title":"corenlp is vulnerable to Improper Restriction of XML External Entity Reference","description":"corenlp is vulnerable to Improper Restriction of XML External Entity Reference","published":"2022-01-17T07:15:07.000Z","lastModified":"2026-06-17T04:20:13.000Z","status":"Analyzed","sourceIdentifier":"security@huntr.dev","cvss":{"version":"3.1","score":9.8,"severity":"CRITICAL","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"},"cwe":["CWE-611"],"affected":["stanford/corenlp"],"epss":{"score":0.01217,"percentile":0.68396,"date":"2026-10-26","history":[]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"high","text":"High impact if exploited, but EPSS currently rates exploitation as unlikely (1.22%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit."},"changes":[],"references":[{"url":"https://github.com/stanfordnlp/corenlp/commit/1940ffb938dc4f3f5bc5f2a2fd8b35aabbbae3dd","tags":["Patch","Third Party Advisory"],"source":"security@huntr.dev"},{"url":"https://huntr.dev/bounties/a717aec2-5646-4a5f-ade0-dadc25736ae3","tags":["Exploit","Third Party Advisory"],"source":"security@huntr.dev"},{"url":"https://github.com/stanfordnlp/corenlp/commit/1940ffb938dc4f3f5bc5f2a2fd8b35aabbbae3dd","tags":["Patch","Third Party Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://huntr.dev/bounties/a717aec2-5646-4a5f-ade0-dadc25736ae3","tags":["Exploit","Third Party Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2022-0239","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}