CVE-2019-14750 json
An issue was discovered in osTicket before 1.10.7 and 1.12.x before 1.12.1.
published 2019-08-07 7 y ago modified 2026-07-10 4 mo ago also EUVD-2019-5890
- cvss
- 6.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 10.9%
- EPSS 10.9% chance of exploitation in 30 days, percentile 95%
- public exploits
- 1
- Exploit-DB, plus a Nuclei check
Summary
An issue was discovered in osTicket before 1.10.7 and 1.12.x before 1.12.1. Stored XSS exists in setup/install.php. It was observed that no input sanitization was provided in the firstname and lastname fields of the application. The insertion of malicious queries in those fields leads to the execution of those queries. This can further lead to cookie stealing or other malicious actions.
Patch / fix
- enhancesoft osticket 1.10.7, 1.12.1
Timeline
- Published
- First public exploit (EDB-47226)
Exploit prediction
10.90% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-47226 osTicket 1.12 - Persistent Cross-Site Scripting webapps, 2019-08-12
- Nuclei template osTicket < 1.12.1 - Cross-Site Scripting nuclei detection template
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
-
github.com
/osTicket/osTicket/commit/c3ba5b78261e07a883ad8fac28c214486c854e12
patch, third-party-advisory
-
exploit-db.com
/exploits/47226
exploit, third-party-advisory, vdb-entry
-
github.com
/osTicket/osTicket/releases/tag/v1.12.1
release-notes, third-party-advisory
-
github.com
/osTicket/osTicket/releases/tag/v1.10.7
release-notes, third-party-advisory
-
packetstormsecurity.com
/files/154005/osTicket-1.12-Cross-Site-Scripting.html
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2019-14750
- NVD CVE-2019-14750
Fencer Vulns 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.