Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A02:2025 - Security Misconfiguration
ASVS 5.0
V13 - Configuration Password externalization from config
|
| Impact | This vulnerability presents exceptionally high real-world risk despite limited publicly available exploit data. The CVSS 9.3 score accurately reflects the severity: AV:L (local attack vector, but standard user access is trivial in enterprise environments with shared workstations), AC:L (no complexity—straightforward file reading and decryption), PR:N (no privilege escalation prerequisites), and S:C/C:H/I:H/A:H (crosses security boundaries with complete confidentiality, integrity, and availability impact). The absence of user interaction (UI:N) makes this automatable. The true risk is elevated in environments where: (1) BRAIN2 connects to critical databases, (2) multiple users access shared systems, (3) the application runs with elevated privileges, or (4) the database account has broad permissions. Without confirmed KEV/CISA inclusion, active exploitation data, or public PoC details, the immediate threat may be lower than CVSS suggests, but the vulnerability is trivial to exploit locally and should be prioritized in any environment using BRAIN2. |
| Exploit ScenarioDerived | An attacker with local access to a Windows system running BRAIN2 (e.g., standard domain user on a shared workstation, contractor with temporary access, or insider threat) navigates to the BRAIN2 application directory, locates the configuration file (typically named config.xml, app.config, settings.ini, or similar), reads it directly (no privilege escalation needed), and extracts the database connection string. If credentials are encrypted, the attacker examines the encryption key (likely hardcoded in the application binary or stored nearby) and decrypts the credentials using standard tools or custom scripts. With the database username, password, and server address now compromised, the attacker connects directly to the backend database server, potentially exfiltrating sensitive data, modifying records, or establishing persistence. In a high-impact scenario, if the BRAIN2 service runs with elevated privileges or the database account has administrative rights, the attacker could escalate to full system compromise or lateral movement across the network. Attack complexity is minimal (minutes to execute) and requires no special tools beyond file system access and basic encryption knowledge. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 15, 2026
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.
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.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
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.
Know when Windows gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Lifecycle Timeline
3DescriptionCVE.org
Standard Windows users can access the configuration file for database access of the BRAIN2 application and decrypt it.
Executive ViewAI
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 lateral movement and unauthorized access to sensitive data stores. This vulnerability bypasses authentication controls and directly threatens confidentiality and integrity of database-backed systems, requiring immediate remediation across all affected deployments.
Apply vendor patch. If immediate patching is not feasible, implement Windows file system access controls (NTFS permissions) to restrict standard user read access to BRAIN2 database configuration files; enable local file encryption (BitLocker/EFS) on directories containing configuration data; deploy host-based monitoring to detect unauthorized access attempts to sensitive configuration files; and implement principle of least privilege to limit local user account permissions.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio
Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in
A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr
Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables
Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker
An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote
FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit
Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio
Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/
React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo
Command injection in the Windows Shell lets remote, unauthenticated attackers bypass a Windows security feature and then
External control of file name or path in Windows NTLM allows an unauthorized attacker to perform spoofing over a network
EUVD-2025-18871
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB