CVE-2024-55546: ORing IAP-420 · XSS or 'Cross-site Scripting'
Affects ORing IAP-420Source CVE Database V5
Not known to be exploited · CVSS 7.1 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:L/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Dec 2024
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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ORing IAP-420 | Affected
| Fixed in– |
AI-suggested
1. Immediately restrict access to the ORing IAP-420 web interface to trusted internal networks using network segmentation and firewall rules. 2. Implement VPN or secure tunnels for remote management to prevent direct exposure of the device interface to the internet. 3. Monitor and audit device logs for unusual activity indicative of attempted XSS exploitation or unauthorized access. 4. Deploy web application firewalls (WAFs) with rules to detect and block XSS payloads targeting the device's management interface. 5. Regularly review and sanitize all user inputs and configurations entered into the device to minimize injection opportunities. 6. Engage with ORing support channels to obtain firmware updates or patches addressing this vulnerability as soon as they become available. 7. Conduct security awareness training for personnel managing these devices to recognize phishing or social engineering attempts that could facilitate user interaction required for exploitation. 8. Consider temporary disabling of web interface features that accept user input if patching is delayed. 9. Integrate vulnerability scanning into regular security assessments to detect vulnerable device versions in the environment.
Description
Missing input validation in the ORing IAP-420 web-interface allows stored Cross-Site Scripting (XSS).This issue affects IAP-420 version 2.01e and below.