CVE-2018-19917 json
Microweber XSS Vulnerability
published 2019-03-17 7 y ago modified 2026-06-17 4 mo ago also GHSA-582j-m369-hj2f , EUVD-2022-2528
- cvss
- 6.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
Microweber 1.0.8 has reflected cross-site scripting (XSS) vulnerabilities.
Exploit prediction
1.58% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- packetstormsecurity.com http://packetstormsecurity.com/files/151005/Microweber-1.0.8-Cross-Site-Scripting.html 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 |
| GitHub | 3.0 | 6.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | microweber/microweber | <=1.0.8 |
no fix listed |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
packetstormsecurity.com
/files/151005/Microweber-1.0.8-Cross-Site-Scripting.html
web, exploit, third-party-advisory, vdb-entry
-
seclists.org
/fulldisclosure/2019/Jan/12
web, mailing-list, third-party-advisory
-
seclists.org
/fulldisclosure/2019/Jan/25
web, mailing-list, third-party-advisory
-
github.com
/microweber/microweber/commits/master
third-party-advisory
-
netsparker.com
/web-applications-advisories/ns-18-038-reflected-cross-site-scripting-in-microweber/
third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2018-19917
advisory
-
github.com
/microweber/microweber
package
-
netsparker.com
/web-applications-advisories/ns-18-038-reflected-cross-site-scripting-in-microweber
web
Sources
- CVE List CVE-2018-19917
- GitHub Advisory GHSA-582j-m369-hj2f
- NVD CVE-2018-19917
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.