CVE-2025-30518
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 · uneditedIncorrect default permissions for some Intel(R) PresentMon before version 2.3.1 within Ring 3: User Applications may allow an escalation of privilege. Unprivileged software adversary with an authenticated user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires active user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.
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 confidenceIntel PresentMon before version 2.3.1 has incorrect default permissions in its user-mode application (Ring 3), allowing an unprivileged but authenticated local user to potentially escalate privileges via file/permission manipulation that can be exploited with high complexity and active user interaction.
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
- Local
- Complexity
- High
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/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.
-
Locate Intel PresentMon installationSearch for 'PresentMon' in Program Files directories or check common installation paths like C:\Program Files\Intel\PresentMon or C:\Program Files (x86)\Intel\PresentMon. Use Get-ChildItem -Recurse -Filter '*PresentMon*' or similar directory search commands.Affected if PresentMon is found installed on the system
-
Identify installed versionLocate the PresentMon.exe file and check its properties, or run 'PresentMon --version' or 'PresentMon -v' from the installation directory to retrieve the version number.Affected if The version displayed is before 2.3.1 (e.g., 2.3.0, 2.2.x, or any version number less than 2.3.1)
-
Verify file permissions on application directoryRight-click the PresentMon installation folder, go to Properties > Security, or use icacls command (e.g., icacls 'C:\Program Files\Intel\PresentMon') to inspect who has write/modify permissions.Affected if Non-administrative users or unprivileged accounts have Write, Modify, or Full Control permissions to the application directory or its executables
-
Check for permission misconfigurationReview ACLs for the PresentMon.exe file specifically using 'icacls PresentMon.exe' and look for entries granting access to Users group or authenticated users with elevated permissions.Affected if Authenticated users or the Users group have permissions beyond Read/Execute on the executable or its parent folder
If Intel PresentMon is installed with a version lower than 2.3.1 AND non-admin users have write or modify access to the application directory or executable, the environment is vulnerable to this privilege escalation flaw.
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.
dbcve · scopedUpgrade Intel PresentMon to version 2.3.1 or later to obtain corrected default permissions; review file system permissions on the application directory as an interim measure.
2.3.1
- Upgrade Intel(R) PresentMon to version 2.3.1 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30518 — 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-30518 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