Skip to main content
CVE-2024-28141VulnerabilityPublished Updated

CVE-2024-28141: Image Access Scan2Net · Cross-Site Request Forgery (CSRF)

Affects Image Access Scan2NetSource CVE Database V5

0

Not known to be exploited · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% 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:U/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 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

To mitigate CVE-2024-28141, organizations should implement several specific measures: 1) Apply any available vendor patches or updates as soon as they are released. 2) If patches are not yet available, deploy web application firewalls (WAFs) with rules to detect and block CSRF attack patterns and suspicious HTTP requests targeting Scan2Net. 3) Configure Scan2Net or its hosting environment to enforce strict SameSite cookie attributes to reduce CSRF risk. 4) Implement network segmentation to isolate Scan2Net devices from general user networks, limiting exposure. 5) Educate users about phishing and social engineering risks to reduce the likelihood of clicking malicious links. 6) Monitor logs for unusual administrative actions or account creations. 7) Consider additional authentication factors for administrative actions to reduce risk from forged requests. 8) Review and harden web server and application configurations to enforce origin and referer header checks where possible. These steps go beyond generic advice by focusing on compensating controls and user awareness tailored to this vulnerability’s exploitation vector.

Description

The web application is not protected against cross-site request forgery attacks. Therefore, an attacker can trick users into performing actions on the application when they visit an attacker-controlled website or click on a malicious link. E.g.an attacker can forge malicious links to reset the admin password or create new users.

References

Community reviews

Loading reviews…