Skip to main content
VulnerabilityPublished

CVE-2025-1711: Endress+Hauser MEAC300-FNADE4 · Use of Default Credentials

Affects Endress+Hauser MEAC300-FNADE4Source CVE Database V5

0

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

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

What to do

Affected software

ProductAffectedFixed in
Endress+Hauser Endress+Hauser MEAC300-FNADE4Affected
  • =0
Fixed in–

AI-suggested

To mitigate this vulnerability effectively, European organizations should: 1) Immediately audit all MEAC300-FNADE4 devices to identify instances where default credentials are still in use. 2) Replace all default credentials with strong, unique passwords for each service and scope within the device to prevent credential reuse. 3) Implement strict network segmentation and access controls to limit network exposure of these devices, restricting access only to authorized personnel and systems. 4) Monitor network traffic and device logs for unusual authentication attempts or access patterns that could indicate exploitation attempts. 5) Engage with Endress+Hauser support to obtain any forthcoming patches or firmware updates addressing this issue and plan timely deployment once available. 6) Incorporate credential management policies into operational technology (OT) security frameworks, ensuring that default credentials are never deployed in production environments. 7) Conduct regular security training for OT staff emphasizing the risks of default credentials and the importance of credential hygiene. These steps go beyond generic advice by focusing on device-specific credential management, network controls tailored to industrial environments, and proactive monitoring.

Description

Multiple services of the DUT as well as different scopes of the same service reuse the same credentials.

References

Community reviews

Loading reviews…