VulnerabilityPublished 3 Jul 2025

CVE-2025-27450: Endress+Hauser MEAC300-FNADE4 · Sensitive Cookie in HTTPS Session Without 'Secure' Attribute

Affects Endress+Hauser MEAC300-FNADE4Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 27 Oct 2026, 17:11 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 22% 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:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Endress+Hauser Endress+Hauser MEAC300-FNADE4	Affected =0	Fixed in–

AI-suggested

To mitigate this vulnerability, organizations should prioritize the following actions: 1) Apply vendor patches or firmware updates once available to ensure cookies are set with the Secure attribute, enforcing HTTPS-only transmission. 2) Enforce strict HTTPS usage by disabling HTTP access to the device’s web interface, including redirecting HTTP requests to HTTPS and using HSTS (HTTP Strict Transport Security) headers. 3) Implement network-level controls such as firewall rules and segmentation to restrict access to the MEAC300-FNADE4 device only to trusted hosts and networks, minimizing exposure to untrusted or public networks. 4) Educate users to avoid accessing the device over unsecured or public Wi-Fi networks and to verify HTTPS connections before entering credentials or interacting with the device. 5) Monitor network traffic for signs of session hijacking attempts or unusual access patterns. 6) Consider deploying web application firewalls (WAFs) or intrusion detection systems (IDS) that can detect anomalous HTTP traffic or cookie misuse. 7) Review and enhance overall OT security policies to include secure cookie handling and session management best practices.

Description

The Secure attribute is missing on multiple cookies provided by the MEAC300-FNADE4. An attacker can trick a user to establish an unencrypted HTTP connection to the server and intercept the request containing the PHPSESSID cookie.

Impact

For European organizations, particularly those in industrial sectors such as manufacturing, utilities, and process automation, this vulnerability poses a risk of unauthorized access to critical control devices. The MEAC300-FNADE4 is likely deployed in operational technology (OT) environments where confidentiality breaches can lead to exposure of sensitive operational data or unauthorized control commands. An attacker intercepting session cookies could impersonate legitimate users, potentially disrupting monitoring or control functions indirectly. While the vulnerability does not directly enable command injection or denial of service, session hijacking in industrial control systems can have cascading effects on operational integrity and safety. European organizations with remote or web-accessible interfaces to such devices are at higher risk, especially if users access the device over insecure networks or if internal network segmentation is weak. The absence of the Secure cookie attribute also indicates potential gaps in secure development practices, which may reflect broader security posture concerns.

CWE-614Sensitive Cookie in HTTPS Session Without 'Secure' Attribute (opens in a new tab)
Variant weaknessOWASP Top 10 A02:2025: Security Misconfiguration (opens in a new tab)
The Secure attribute for sensitive cookies in HTTPS sessions is not set.
Implementation
Always set the secure attribute when the cookie should be sent via HTTPS only.
OWASP Cheat Sheets
Cross-Site Request Forgery Prevention (opens in a new tab)
Session Management (opens in a new tab)
OWASP ASVS 4.0.3
V3.4.1 (opens in a new tab)
V8.3.1 (opens in a new tab)
V9.2.2 (opens in a new tab)
Attack patterns
Session Sidejacking (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Jul 2025, 11:56 UTC

WeaknessesCWE-614

Technical details

References

Community reviews

Related threats