CVE-2025-0867
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe standard user uses the run as function to start the MEAC applications with administrative privileges. To ensure that the system can startup on its own, the credentials of the administrator were stored. Consequently, the EPC2 user can execute any command with administrative privileges. This allows a privilege escalation to the administrative level.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA standard user (EPC2) can execute arbitrary commands with administrative privileges by leveraging stored administrator credentials that were configured to enable automatic MEAC application startup. This is a critical privilege escalation vulnerability stemming from insecure credential storage accessible to unprivileged users.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if MEAC application is installedSearch for MEAC-related executables, services, or scheduled tasks on the system using: dir /s /b C:\*meac* or search in Program Files directoriesAffected if MEAC application is present on the system
-
Check for stored administrative credentialsExamine Windows Credential Manager or stored password configurations used by MEAC. Look for saved credentials targeting administrative accounts in: cmdkey /list or in MEAC configuration filesAffected if Stored credentials for administrative accounts exist and are accessible to the current user context
-
Verify MEAC automatic startup configurationCheck MEAC application startup settings in Windows Task Scheduler, services, or registry Run keys for automatic execution configurationsAffected if MEAC is configured for automatic startup at logon or system boot
-
Test privilege escalation pathAs a standard user (EPC2), attempt to invoke the stored credential mechanism used by MEAC to execute a command with elevated privilegesAffected if A standard user can leverage the stored credentials to run commands with administrative privileges
-
Review credential storage permissionsCheck file system permissions on MEAC configuration files and credential storage locations to verify unprivileged users can read or modify themAffected if Standard users have read or execute access to credential storage locations used by MEAC
A user is affected if MEAC application is installed with stored administrative credentials that standard users can access and leverage for privilege escalation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRemove stored administrative credentials from the system and reconfigure MEAC application startup to use proper privilege management mechanisms such as scheduled tasks with service accounts possessing only the minimum required privileges.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0867 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-0867 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data