What is the CVSS score of EUVD-2025-18871?

EUVD-2025-18871 has a CVSS 3.1 base score of 9.3 (Critical). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

Which versions of Windows are affected by EUVD-2025-18871?

CVE-2025-6513 is a critical privilege escalation flaw in BRAIN2 that allows any standard Windows user with local system access to extract unencrypted database credentials, potentially enabling…. A patch is available.

How to fix or mitigate EUVD-2025-18871?

Within 24 hours: Identify all systems running BRAIN2 and verify current version against vendor advisory to confirm exposure. Within 7 days: Apply vendor-released patch to all affected BRAIN2 instances and validate successful deployment. Within 30 days: Conduct credential audit on all exposed database accounts, rotate compromised credentials, and review access logs for unauthorized database access attempts.

Windows EUVD-2025-18871

| CVE-2025-6513 CRITICAL

Password in Configuration File (CWE-260)

2025-06-23 0beee27a-7d8c-424f-8e46-ac453fa147e6

Windows Privilege Escalation Information Disclosure Microsoft

9.3

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

9.3 CRITICAL

AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Updated

Apr 16, 2026 - 05:53 EUVD-patch-fix

executive_summary

Re-analysis Queued

Apr 16, 2026 - 05:29 backfill_euvd_patch

patch_released

Patch available

Apr 16, 2026 - 05:29 EUVD

3.06

EUVD ID Assigned

Mar 15, 2026 - 22:10 euvd

EUVD-2025-18871

Analysis Generated

Mar 15, 2026 - 22:10 vuln.today

CVE Published

Jun 23, 2025 - 13:15 nvd

CRITICAL 9.3

DescriptionCVE.org

Standard Windows users can access the configuration file for database access of the BRAIN2 application and decrypt it.

AnalysisAI

CVE-2025-6513 is a local privilege escalation vulnerability in the BRAIN2 application where standard Windows users can access and decrypt the application's database configuration file without authentication. This allows unprivileged local users to obtain database credentials and potentially compromise sensitive data, with a CVSS score of 9.3 indicating critical severity. The vulnerability affects system confidentiality, integrity, and availability across trust boundaries.

Technical ContextAI

The vulnerability stems from CWE-260 (Passwords in Configuration Files) combined with improper access controls and weak or predictable encryption. The BRAIN2 application stores database connection credentials in a configuration file that is readable by standard (non-administrative) Windows users, and the encryption scheme protecting these credentials is either absent, weak, or uses hardcoded keys that can be decrypted by local users. The root cause is inadequate file system permissions (likely the config file lacks proper ACLs restricting access to SYSTEM or Administrators only) and potentially the use of symmetric encryption with embedded or easily derivable keys rather than secure credential storage mechanisms like Windows Data Protection API (DPAPI) or credential manager integration.

RemediationAI

Immediate mitigations include: (1) Restrict file system permissions on the BRAIN2 configuration file to SYSTEM and Administrators only using Windows ACLs, removing read access for standard users; (2) Move database credentials out of plaintext configuration files and use Windows DPAPI or integrated Windows authentication for database connections; (3) Implement strict access controls on workstations where BRAIN2 runs, limiting local user access where possible; (4) Monitor configuration file access using Windows Event Viewer or EDR solutions. Long-term remediation requires a vendor patch that stores credentials securely (DPAPI encryption at rest, environment variables, or credential manager integration). Organizations should contact the BRAIN2 vendor immediately for patch availability and release timeline. A temporary workaround is to run BRAIN2 service/process with a dedicated service account and restrict local file system access to that account only.