CVE-2019-0186 json
Cross-site Scripting in Apache Pluto Chatroom demo
published 7y ago modified 4mo ago also GHSA-w47g-4vrc-m3w2 , EUVD-2022-5492
- cvss
- 6.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 20.6%
- EPSS 20.6% chance of exploitation in 30 days, percentile 97%
- public exploits
- 1
- Exploit-DB
Summary
The input fields of the Apache Pluto "Chat Room" demo portlet 3.0.0 and 3.0.1 are vulnerable to Cross-Site Scripting (XSS) attacks. Mitigation: * Uninstall the ChatRoomDemo war file - or - * migrate to version 3.1.0 of the chat-room-demo war file
Patch / fix
- maven org.apache.portals.pluto:chatRoomDemo 3.1.0
Is CVE-2019-0186 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
- First public exploit (EDB-46759)
- Published
Exploit prediction
20.65% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-46759 Apache Pluto 3.0.0 / 3.0.1 - Persistent Cross-Site Scripting webapps, 2019-04-26
- packetstormsecurity.com http://packetstormsecurity.com/files/152642/Apache-Pluto-3.0.0-3.0.1-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 |
|---|---|---|---|
| maven | org.apache.portals.pluto:chatRoomDemo | >=3.0.0, <3.1.0 |
3.1.0 |
Affected products
- Apache Software Foundation Apache Pluto
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
exploit-db.com
/exploits/46759/
exploit, third-party-advisory, vdb-entry
-
packetstormsecurity.com
/files/152642/Apache-Pluto-3.0.0-3.0.1-Cross-Site-Scripting.html
exploit, third-party-advisory
-
portals.apache.org
/pluto/security.html
web, mitigation, vendor-advisory
-
mail-archives.apache.org
/mod_mbox/portals-pluto-user/201904.mbox/%3CCAAqbB_ev=0KNgZmmNAq2=q11i1GYLGN6J-xCKx8Q8dbxZ4tZYg%40mail.gmail.c
mailing-list
-
openwall.com
/lists/oss-security/2019/04/25/8
mailing-list, web, mitigation, third-party-advisory
-
lists.apache.org
/thread.html/d093e6b0e5f9b3b50928255451afefd8f8fbdcd5bf28a726769a919a%40%3Cpluto-user.portals.apache.org%3E
mailing-list
-
securityfocus.com
/bid/108091
vdb-entry, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-0186
advisory
-
lists.apache.org
/thread.html/d093e6b0e5f9b3b50928255451afefd8f8fbdcd5bf28a726769a919a@%3Cpluto-user.portals.apache.org%3E
web
-
exploit-db.com
/exploits/46759
web
-
mail-archives.apache.org
/mod_mbox/portals-pluto-user/201904.mbox/%3CCAAqbB_ev=0KNgZmmNAq2=q11i1GYLGN6J-xCKx8Q8dbxZ4tZYg@mail.gmail.com
web
Sources
- CVE List CVE-2019-0186
- GitHub Advisory GHSA-w47g-4vrc-m3w2
- NVD CVE-2019-0186
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.