CVE-2025-13051
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 · uneditedWhen the service of ABP and AES is installed in a directory writable by non-administrative users, an attacker can replace or plant a DLL with the same name as one loaded by the service. Upon service restart, the malicious DLL is loaded and executed under the LocalSystem account, resulting in unauthorized code execution with elevated privileges. This issue affects ABP and AES: from ABP 2.0 through 2.0.7.9050, from AES 1.0 through 1.0.6.8290.
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 DLL hijacking vulnerability in ABP and AES services allows non-administrative users to write to the installation directory and plant a malicious DLL with the same name as one loaded by the service. When the service restarts, it loads the attacker-controlled DLL under the LocalSystem account, achieving privilege escalation to NT AUTHORITY\SYSTEM.
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
- Low
- Privileges
- Low
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 ABP or AES services are installedOpen Services console (services.msc) or run 'sc query' command to list all services. Look for service names containing 'ABP' or 'AES'.Affected if ABP or AES service exists on the system
-
Locate the service executable pathFor each identified service, run 'sc qc <service_name>' to retrieve the binary path. Alternatively, use 'wmic service where "name like '%ABP%' or name like '%AES%'" get name,pathname'Affected if Service binary path is returned from the query
-
Extract the service installation directoryParse the binary path from step 2 to isolate the directory (remove the executable filename). For example, if path is 'C:\Program Files\Vendor\ABP\service.exe', the directory is 'C:\Program Files\Vendor\ABP'Affected if Directory path is successfully extracted
-
Check directory permissions for write accessRight-click the installation directory, go to Properties > Security tab. Or run 'icacls "<directory_path>"' from command prompt to view ACLs.Affected if Non-administrative users or the 'Users' group are listed with Write or Full Control permissions
-
Verify if standard user accounts can create files in the directoryAttempt to create a test file using a standard (non-admin) user account, or review icacls output for (WD) or (F) permissions granted to non-admin SIDsAffected if Standard users can write files to the service installation directory
User is affected if ABP or AES service is installed and its installation directory grants write permissions to non-administrative users.
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 dataRestrict write permissions on the service installation directory to only administrators, ensuring non-privileged users cannot modify or add DLLs. Consider reinstalling the service in a properly secured directory location with restricted permissions.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13051 — 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-13051 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