CVE-2025-13818
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 · uneditedLocal privilege escalation vulnerability via insecure temporary batch file execution in ESET Management Agent
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 · moderate confidenceLocal privilege escalation vulnerability in ESET Management Agent where the software creates and executes temporary batch files insecurely, allowing a local attacker to inject malicious commands that execute with elevated SYSTEM privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 12.5.2104.0CVSS 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
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/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.
-
Identify ESET Management Agent installation and versionOpen Windows Registry and navigate to HKLM\SOFTWARE\ESET\ESET Security\CurrentVersion\Info (or check Programs and Features for 'ESET Management Agent'). Record the installed version number.Affected if The installed version is 12.5.2104.0 or lower.
-
Locate ESET temporary batch filesSearch system temp directories (C:\Windows\Temp, C:\Users\<user>\AppData\Local\Temp) for .bat or .cmd files with ESET-related names or random alphanumeric patterns. Use command: dir /s /b C:\Windows\Temp\*.bat 2>nul & dir /s /b C:\Users\*\AppData\Local\Temp\*.bat 2>nulAffected if Unexpected batch files exist in temp directories, especially with names suggesting automated creation or execution.
-
Review process execution logs for ESET componentCheck Windows Event Viewer under Application and Services Logs > ESET > Common for events around scheduled tasks or updater activity, which trigger the vulnerable temp file execution.Affected if Events show frequent execution of batch scripts from temp locations.
-
Audit temp directory permissionsRight-click temp folders (C:\Windows\Temp, %TEMP%) > Properties > Security tab. Verify that non-admin users lack Write/Modify permissions to create new files.Affected if Users with low privileges can write to system temp directories, enabling the injection attack.
You are affected if ESET Management Agent version 12.5.2104.0 or lower is installed and low-privilege users have write access to temp directories where batch files may be created.
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 dataApply vendor patches for ESET Management Agent when available; in the interim, enforce strict file permissions on temp directories and monitor for unauthorized batch file creation in system locations.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13818 — 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-13818 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