CVE-2023-46471: Space Applications Services Yamcs v · Cross-site Scripting
Source CVE Database V5
Not known to be exploited · CVSS 5.4 Medium.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
Organizations should implement strict input validation and output encoding for all user-supplied data in the ScriptViewer component to prevent script injection. Until an official patch is released, applying web application firewalls (WAFs) with custom rules to detect and block malicious script payloads targeting the 'scriptContainer' parameter is recommended. Restricting access to the Yamcs interface to trusted users and networks can reduce exposure. Additionally, educating users about the risks of interacting with untrusted links or inputs within the application can mitigate social engineering vectors. Monitoring logs for unusual script execution attempts or anomalies in user behavior can help detect exploitation attempts early. Finally, organizations should track vendor communications for patches or updates addressing this vulnerability and apply them promptly once available.
Description
Cross Site Scripting vulnerability in Space Applications Services Yamcs v.5.8.6 allows a remote attacker to execute arbitrary code via the text variable scriptContainer of the ScriptViewer.