CVE-2019-13234 json
XSS in search engine
published 7y ago modified 4mo ago also GHSA-fxp8-7h5w-h235 , EUVD-2019-0748
- cvss
- 6.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.9%
- EPSS 2.9% chance of exploitation in 30 days, percentile 87%
- public exploits
- 1
- Exploit-DB
Summary
In the Alkacon OpenCms Apollo Template 10.5.4 and 10.5.5, there is XSS in the search engine.
Patch / fix
- maven org.opencms:opencms-core 11.0.1
Is CVE-2019-13234 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- Published
- First public exploit (EDB-47338)
Exploit prediction
2.90% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-47338 Alkacon OpenCMS 10.5.x - Cross-Site Scripting webapps, 2019-09-02
- aetsu.github.io https://aetsu.github.io/OpenCms 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 |
|---|---|---|---|
| maven | org.opencms:opencms-core | <11.0.1 |
11.0.1 |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/alkacon/apollo-template/commits/branch_10_5_x
web, patch
-
aetsu.github.io
/OpenCms
web, exploit, third-party-advisory
-
packetstormsecurity.com
/files/154298/Alkacon-OpenCMS-10.5.x-Cross-Site-Scripting.html
web
-
nvd.nist.gov
/vuln/detail/CVE-2019-13234
advisory
Sources
- CVE List CVE-2019-13234
- GitHub Advisory GHSA-fxp8-7h5w-h235
- NVD CVE-2019-13234
Fencer Intel 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.