CVE-2018-19170: XSS
First published: Sun Nov 11 2018(Updated: )
In JPress v1.0-rc.5, there is stored XSS via each of the first three input fields to the starter-tomcat-1.0/admin/setting URI, as demonstrated by the web_name parameter.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| openMairie Openpresse | =1.0-rc5 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2018-19170?
CVE-2018-19170 has a medium severity rating due to its potential for stored XSS attacks.
How do I fix CVE-2018-19170?
To fix CVE-2018-19170, sanitize all input fields in the starter-tomcat-1.0/admin/setting URI to prevent stored XSS.
What versions of JPress are affected by CVE-2018-19170?
CVE-2018-19170 affects JPress version 1.0-rc.5.
What type of vulnerability is CVE-2018-19170?
CVE-2018-19170 is a stored cross-site scripting (XSS) vulnerability.
Where in JPress can CVE-2018-19170 be exploited?
CVE-2018-19170 can be exploited through the first three input fields to the starter-tomcat-1.0/admin/setting URI.
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/last-modified-date
- agent/severity
- agent/author
- agent/description
- agent/event
- agent/first-publish-date
- agent/source
- agent/weakness
- agent/tags
- agent/softwarecombine
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/jpress
- canonical/openmairie openpresse
- version/openmairie openpresse/1.0-rc5