CVE-2019-13239 json
inc/user.class.php in GLPI before 9.4.3 allows XSS via a user picture.
published 2019-07-04 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-4746
- cvss
- 6.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 71%
- public exploits
- 0
- none known
Summary
inc/user.class.php in GLPI before 9.4.3 allows XSS via a user picture.
Patch / fix
- glpi-project glpi 9.4.3
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2019-13239 updated cvss 6.1
glpi: XSS via user picture in inc/user.class.php
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.33% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- synacktiv.com https://www.synacktiv.com/ressources/advisories/GLPI_9.4.0_stored_XSS.pdf 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
-
github.com
/glpi-project/glpi/commit/c2aa7a7cd6af28be3809acc7e7842d2d2008c0fb
patch, third-party-advisory
-
synacktiv.com
/ressources/advisories/GLPI_9.4.0_stored_XSS.pdf
exploit, third-party-advisory
-
github.com
/glpi-project/glpi/releases/tag/9.4.3
release-notes, third-party-advisory
Sources
- CVE List CVE-2019-13239
- NVD CVE-2019-13239
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.