CVE-2019-20008 json
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 resu…
published 2019-12-26 6 y ago modified 2026-06-17 4 mo ago also PYSEC-2019-112 , EUVD-2019-0105
- cvss
- 5.4
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 60%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi pyarchery 1.3.0
- archerysec archery 1.3
Exploit prediction
0.92% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/archerysec/archerysec/issues/338 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:N/I:P/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | pyarchery | <1.3.0 |
1.3.0 |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/archerysec/archerysec/issues/338
exploit, issue-tracking, third-party-advisory, report
-
github.com
/archerysec/archerysec/releases/tag/v1.3
release-notes, third-party-advisory, web
-
github.com
/archerysec/archerysec/compare/archerysec-v1.2...v1.3
release-notes, third-party-advisory, web
Sources
- CVE List CVE-2019-20008
- NVD CVE-2019-20008
- OSV PYSEC-2019-112
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.