Endress+Hauser MEAC300-FNADE4 EPC2 Windows authorization

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.1$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in Endress+Hauser MEAC300-FNADE4. Affected by this issue is some unknown functionality of the component EPC2 Windows. The manipulation leads to authorization. This vulnerability is uniquely identified as CVE-2025-27461. It is possible to launch the attack on the physical device. No exploit exists.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Endress+Hauser MEAC300-FNADE4 (affected version unknown). This issue affects an unknown functionality of the component EPC2 Windows. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

During startup, the device automatically logs in the EPC2 Windows user without requesting a password.

The identification of this vulnerability is CVE-2025-27461 since 02/26/2025. The exploitation is known to be easy. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-19867). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.1
VulDB Meta Temp Score: 7.1

VulDB Base Score: 6.8
VulDB Temp Score: 6.8
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 6.8
NVD Vector: 🔒

CNA Base Score: 7.6
CNA Vector (SICK AG): 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Authorization
CWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔒
ATT&CK: 🔒

Physical: Yes
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔒

Timelineinfo

02/26/2025 CVE reserved
07/03/2025 +126 days Advisory disclosed
07/03/2025 +0 days VulDB entry created
02/06/2026 +218 days VulDB entry last update

Sourcesinfo

Status: Not defined

CVE: CVE-2025-27461 (🔒)
GCVE (CVE): GCVE-0-2025-27461
GCVE (VulDB): GCVE-100-314777
EUVD: 🔒

Entryinfo

Created: 07/03/2025 16:11
Updated: 02/06/2026 17:36
Changes: 07/03/2025 16:11 (59), 07/03/2025 17:17 (1), 02/06/2026 17:36 (12)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!