Skip to main content
VulnerabilityPublished

CVE-2025-46414: EG4 12kPV · CWE-307

Affects EG4 12kPVSource CVE Database V5

0

Not known to be exploited · CVSS 8.1 High.

Data as of 26 Oct 2026, 14:05 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Aug 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
EG4 Electronics EG4 12kPVAffected
  • *
Fixed in–

AI-suggested

European organizations should ensure that all EG4 12kPV devices are updated with the server-side patch released on April 6, 2025, which addresses the brute-force vulnerability by implementing proper attempt restrictions. Network segmentation should be employed to isolate these devices from general IT networks and restrict access to trusted management systems only. Implementing intrusion detection systems (IDS) and monitoring for unusual authentication attempts or repeated PIN entry failures can provide early warning of brute-force attempts. Organizations should also enforce strict access controls around device serial numbers and related credentials to prevent attackers from obtaining valid identifiers. Where possible, multi-factor authentication (MFA) mechanisms should be layered on top of device authentication to reduce reliance on PINs alone. Additionally, logging and auditing of authentication attempts should be enabled and regularly reviewed to detect and respond to suspicious activities promptly.

Description

The affected product does not limit the number of attempts for inputting the correct PIN for a registered product, which may allow an attacker to gain unauthorized access using brute-force methods if they possess a valid device serial number. The API provides clear feedback when the correct PIN is entered. This vulnerability was patched in a server-side update on April 6, 2025.

References

Community reviews

Loading reviews…