CVE-2019-17625: There is a stored XSS in Rambox 0.6.9 that can lead to code execution
CVE-2019-17625 is a critical-severity flaw (CVSS 9.0) affecting rambox. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
There is a stored XSS in Rambox 0.6.9 that can lead to code execution. The XSS is in the name field while adding/editing a service. The problem occurs due to incorrect sanitization of the name field when being processed and stored. This allows a user to craft a payload for Node.js and Electron, such as an exec of OS commands within the onerror attribute of an IMG element.
Why this priority
- Critical severity
- Public exploit reference
No fix is published yet: follow the downgrade or mitigation steps.
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2019-17625?
rambox: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2019-17625 being exploited?
CVE-2019-17625 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2019-17625 affect?
CVE-2019-17625 affects rambox. Severity is critical (CVSS 9.0). There is a stored XSS in Rambox 0.6.9 that can lead to code execution. The XSS is in the name field while adding/editing a service. The problem occurs due to incorrect sanitization of the name field when being processed and stored. This all
How urgent is CVE-2019-17625?
Priority 58/100. Critical severity; Public exploit reference
Software pages
Node.js vulnerabilities · Electron vulnerabilities