CVE-2019-6504 json
Insufficient output sanitization in the Automic Web Interface (AWI), in CA Automic Workload Automation 12.0 to 12.2, allow attackers to pot…
published 2019-02-06 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-16063
- cvss
- 6.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
Insufficient output sanitization in the Automic Web Interface (AWI), in CA Automic Workload Automation 12.0 to 12.2, allow attackers to potentially conduct persistent cross site scripting (XSS) attacks via a crafted object.
Exploit prediction
2.01% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Affected products
- CA Technologies - A Broadcom Company CA Automic Workload Automation
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
communities.ca.com
/community/product-vulnerability-response/blog/2019/01/24/ca20190124-01-security-notice-for-ca-automic-workloa
vendor-advisory
-
support.ca.com
/us/product-content/recommended-reading/security-notices/CA20190124-01-security-notice-for-ca-automic-workload
vendor-advisory
-
marc.info
/?l=bugtraq&m=154874504200510&w=2
mailing-list, third-party-advisory
-
securityfocus.com
/bid/106755
vdb-entry, third-party-advisory
-
sec-consult.com
/en/blog/advisories/cross-site-scripting-in-ca-automic-workload-automation-web-interface-formerly-automic-auto
third-party-advisory
-
packetstormsecurity.com
/files/151325/CA-Automic-Workload-Automation-12.x-Cross-Site-Scripting.html
third-party-advisory, vdb-entry
-
seclists.org
/fulldisclosure/2019/Jan/61
mailing-list, third-party-advisory
Sources
- CVE List CVE-2019-6504
- NVD CVE-2019-6504
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.