CVE-2016-2046 json
Cross-site scripting (XSS) vulnerability in the UserPortal page in SOPHOS UTM before 9.353 allows remote attackers to inject arbitrary web…
published 2016-02-17 10 y ago modified 2026-06-17 4 mo ago also EUVD-2016-3152
- cvss
- 6.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.8%
- EPSS 2.8% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
Cross-site scripting (XSS) vulnerability in the UserPortal page in SOPHOS UTM before 9.353 allows remote attackers to inject arbitrary web script or HTML via the lang parameter.
Exploit prediction
2.77% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- seclists.org http://seclists.org/fulldisclosure/2016/Feb/60 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/135709/Sophos-UTM-9-Cross-Site-Scripting.html referenced PoC, tagged "exploit" by a source, unverified
- halock.com http://www.halock.com/blog/cve-2016-2046-cross-site-scripting-sophos-utm-9/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
seclists.org
/fulldisclosure/2016/Feb/60
mailing-list, exploit, third-party-advisory
-
packetstormsecurity.com
/files/135709/Sophos-UTM-9-Cross-Site-Scripting.html
exploit, third-party-advisory
-
halock.com
/blog/cve-2016-2046-cross-site-scripting-sophos-utm-9/
exploit, third-party-advisory
-
securitytracker.com
/id/1035048
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2016-2046
- NVD CVE-2016-2046
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.