CVE-2019-0186 — chatRoomDemo
MEDIUMCVE-2019-0186 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in org.apache.portals.pluto:chatRoomDemo. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.apache.portals.pluto:chatRoomDemo — see the affected versions and patch details below.
Cross-site Scripting in Apache Pluto Chatroom demo
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.apache.portals.pluto:chatRoomDemoReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.portals.pluto:chatRoomDemo | ≥ 3.0.0&&< 3.1.0 | 3.1.0org.apache.portals.pluto:chatRoomDemo:3.1.0 |
Affected Products
plutoapacheResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Apache Pluto 3.0.0 / 3.0.1 - Persistent Cross-Site Scripting
by Dhiraj Mishra · Apr 26, 2019
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.portals.pluto:chatRoomDemo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.portals.pluto:chatRoomDemo to 3.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-0186 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2019-0186 in your dependencies?
Find it across Maven, including transitive dependencies.