Skip to main content
CVE-2024-28142VulnerabilityPublished Updated

CVE-2024-28142: Image Access Scan2Net · XSS or 'Cross-site Scripting'

Affects Image Access Scan2NetSource CVE Database V5

0

Not known to be exploited · CVSS 4.7 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
4.7Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Dec 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Image Access GmbH Scan2NetAffected
  • =0
Fixed in–

AI-suggested

1. Immediately restrict network access to Scan2Net devices, ensuring they are not exposed to untrusted networks or the internet. 2. Implement strict access controls and network segmentation to limit who can reach the Scan2Net management interface. 3. Monitor and audit the 'File Name' page and related user settings for suspicious or unexpected input values, particularly those containing script tags or unusual characters. 4. Educate administrators and users to avoid clicking on suspicious links or viewing untrusted pages within Scan2Net interfaces. 5. Contact Image Access GmbH for official patches or updates addressing CVE-2024-28142 and apply them promptly once available. 6. As a temporary workaround, disable or limit the use of wildcard characters in file name inputs if possible. 7. Employ web application firewalls (WAFs) or intrusion detection systems (IDS) that can detect and block XSS payloads targeting Scan2Net devices. 8. Regularly review and update device firmware and software to incorporate security fixes. 9. Conduct internal penetration testing focusing on Scan2Net devices to identify and remediate similar input validation issues.

Description

Due to missing input sanitization, an attacker can perform cross-site-scripting attacks and run arbitrary Javascript in the browser of other users. The "File Name" page (/cgi/uset.cgi?-cfilename) in the User Settings menu improperly filters the "file name" and wildcard character input field. By exploiting the wildcard character feature, attackers are able to store arbitrary Javascript code which is being triggered if the page is viewed afterwards, e.g.by higher privileged users such as admins. This attack can even be performed without being logged in because the affected functions are not fully protected. Without logging in, only the file name parameter of the "Default" User can be changed.

References

Community reviews

Loading reviews…