Skip to main content
CVE-2025-3705VulnerabilityPublished

CVE-2025-3705: Frauscher FDS102 · OS Command Injection

Affects Frauscher FDS102Source CVE Database V5

0

Not known to be exploited · CVSS 6.8 Medium.

Data as of 26 Oct 2026, 06:26 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Jul 2025

  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
Frauscher FDS102Affected
  • =0.0.0
Fixed in–

AI-suggested

1. Enforce strict physical security controls around devices using Frauscher FDS102 to prevent unauthorized access to USB ports or the devices themselves. 2. Implement USB port control policies, such as disabling USB ports where not needed or using hardware locks to prevent unauthorized USB device insertion. 3. Monitor and audit device configuration changes and USB usage logs to detect unusual activity promptly. 4. Until a patch is available, avoid loading configuration files from untrusted USB drives; use secure, verified methods for configuration updates. 5. Segment networks to isolate these devices from critical IT infrastructure to limit potential lateral movement if compromise occurs. 6. Engage with Frauscher for updates on patches or firmware upgrades addressing this vulnerability and plan for timely deployment once available. 7. Conduct regular security training for personnel to recognize and report suspicious physical access or tampering attempts. 8. Consider deploying endpoint detection and response (EDR) solutions capable of monitoring device behavior anomalies related to configuration changes or command execution.

Description

A physical attacker with no privileges can gain full control of the affected device due to improper neutralization of special elements used in an OS Command ('OS Command Injection') when loading a config file from a USB drive.

References

Community reviews

Loading reviews…