Skip to main content
VulnerabilityPublished

CVE-2025-5113: Diviotec nbr222p · Command Injection

Affects Diviotec nbr222pSource CVE Database V5

0

Not known to be exploited · CVSS 8.6 High.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 4.0 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
8.2% chance of exploitation in 30 days – higher than 94% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Jun 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Diviotec nbr222pAffected
  • =0
Fixed in–

AI-suggested

1. Immediate network segmentation: Isolate Diviotec nbr222p devices on dedicated VLANs or network segments with strict access controls to limit exposure to trusted users and systems only. 2. Implement strong network-level authentication and monitoring: Use network access control (NAC) solutions to enforce authentication before access and monitor traffic for anomalous command injection patterns. 3. Replace or disable vulnerable endpoints: If possible, disable the vulnerable web interface endpoint or replace the device with a secure alternative until a patch is available. 4. Change default or hardcoded passwords: Although hardcoded passwords are difficult to change, check for any available configuration options or firmware updates that allow password modification; otherwise, treat devices as compromised and isolate them. 5. Employ intrusion detection/prevention systems (IDS/IPS): Deploy IDS/IPS with signatures or heuristics to detect command injection attempts targeting Diviotec devices. 6. Monitor logs and network traffic for suspicious activities related to the device. 7. Engage with Diviotec support or vendor channels to request patches or firmware updates addressing this vulnerability. 8. Develop incident response plans specifically for potential compromise of these devices.

Description

The Diviotec professional series exposes a web interface. One endpoint is vulnerable to arbitrary command injection and hardcoded passwords are used.

References

Community reviews

Loading reviews…