CVE-2018-11512 json
Stored cross-site scripting (XSS) vulnerability in the "Website's name" field found in the "Settings" page under the "General" menu in Crea…
published 2018-05-28 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-3541
- cvss
- 4.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 81%
- public exploits
- 1
- Exploit-DB
Summary
Stored cross-site scripting (XSS) vulnerability in the "Website's name" field found in the "Settings" page under the "General" menu in Creatiwity wityCMS 0.6.1 allows remote attackers to inject arbitrary web script or HTML via a crafted website name by doing an authenticated POST HTTP request to admin/settings/general.
Patch / fix
- github.com/Creatiwity/wityCMS@7967e5b commit
- exploit-db.com/exploits/44790/ advisory
- github.com/Creatiwity/wityCMS/issues/150 advisory
Timeline
- First public exploit (EDB-44790)
- Published
Exploit prediction
2.06% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-44790 wityCMS 0.6.1 - Cross-Site Scripting webapps, 2018-05-28
- github.com https://github.com/Creatiwity/wityCMS/issues/150 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 4.8 | CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/Creatiwity/wityCMS/commit/7967e5bf15b4d2ee6b85b56e82d7e1229147de44
patch
-
exploit-db.com
/exploits/44790/
exploit, patch, third-party-advisory, vdb-entry
-
github.com
/Creatiwity/wityCMS/issues/150
exploit, issue-tracking, patch, third-party-advisory
Sources
- CVE List CVE-2018-11512
- NVD CVE-2018-11512
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.