CVE-2014-1695 json
Cross-site scripting (XSS) vulnerability in Open Ticket Request System (OTRS) 3.1.x before 3.1.20, 3.2.x before 3.2.15, and 3.3.x before 3.…
published 2014-02-28 12 y ago modified 2026-06-17 4 mo ago also EUVD-2014-1769
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.9%
- EPSS 4.9% chance of exploitation in 30 days, percentile 92%
- public exploits
- 1
- Exploit-DB
Summary
Cross-site scripting (XSS) vulnerability in Open Ticket Request System (OTRS) 3.1.x before 3.1.20, 3.2.x before 3.2.15, and 3.3.x before 3.3.5 allows remote attackers to inject arbitrary web script or HTML via a crafted HTML email.
Patch / fix
- otrs2 Debian 11 3.3.5-1
debian advisories DEBIAN-CVE-2014-1695
- otrs openSUSE Tumbleweed 3.3.14-37.1
opensuse advisories openSUSE-SU-2024:10073-1
Timeline
- Published
- First public exploit (EDB-36842)
Exploit prediction
4.90% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-36842 OTRS < 3.1.x / < 3.2.x / < 3.3.x - Persistent Cross-Site Scripting webapps, 2015-04-27
- packetstormsecurity.com http://packetstormsecurity.com/files/131654/OTRS-3.x-Cross-Site-Scripting.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| 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
-
exploit-db.com
/exploits/36842/
exploit
-
packetstormsecurity.com
/files/131654/OTRS-3.x-Cross-Site-Scripting.html
exploit
-
lists.opensuse.org
/opensuse-updates/2014-03/msg00030.html
vendor-advisory
-
secunia.com
/advisories/57018
third-party-advisory, vendor-advisory
-
otrs.com
/security-advisory-2014-03-xss-issue
vendor-advisory
-
securityfocus.com
/bid/65844
vdb-entry
- adamziaja.com /poc/201401-xss-otrs.html
-
osvdb.org
/103781
vdb-entry
Sources
- CVE List CVE-2014-1695
- NVD CVE-2014-1695
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.