CVE-2023-6401
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 · uneditedA vulnerability classified as problematic was found in NotePad++ up to 8.1. Affected by this vulnerability is an unknown functionality of the file dbghelp.exe. The manipulation leads to uncontrolled search path. An attack has to be approached locally. The identifier VDB-246421 was assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceA DLL hijacking vulnerability exists in NotePad++ versions up to 8.1 involving the dbghelp.exe component. The application loads DLLs from an uncontrolled search path, allowing a local attacker to place a malicious DLL in a location where NotePad++ will load it, potentially achieving code execution with the application's 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<= 8.1CVSS 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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Check Notepad++ installed versionOpen Notepad++ and go to Help > About, or check the executable properties (notepad++.exe) in the installation folder, or check the Windows registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Notepad++ for the DisplayVersion valueAffected if Version is 8.1 or lower
-
Locate the Notepad++ installation directoryRight-click the Notepad++ shortcut, select Properties, and check the 'Start in' path, or find notepad++.exe in Program Files or a custom installation folderAffected if Directory path is found - needed for next check
-
Verify if dbghelp.exe exists in the Notepad++ folderCheck the Notepad++ installation directory for a file named dbghelp.exe - this is the component involved in the DLL hijacking vulnerabilityAffected if dbghelp.exe is present in the Notepad++ installation folder
-
Check if the Notepad++ directory has weak permissionsRight-click the Notepad++ installation folder in Windows Explorer, select Properties > Security, and review which users or groups have Write or Modify permissions - particularly check if Users or Authenticated Users have write accessAffected if Non-admin users have Write or Modify permissions to the Notepad++ installation directory
User is affected if Notepad++ version is 8.1 or lower, dbghelp.exe exists in the Notepad++ folder, AND the directory is writable by non-admin users who could place a malicious DLL.
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 NotePad++ to a version newer than 8.1 that includes a patched dbghelp.exe, or remove dbghelp.exe if functionality is not required. As a workaround, ensure the NotePad++ directory is not writable by unprivileged users.
Notepad++ 8.2 or later (latest stable release)
- 1. Download the latest version of Notepad++ from the official website (notepad-plus-plus.org)
- 2. Uninstall the current version of Notepad++ if currently installed
- 3. Install the downloaded latest version
- 4. Verify the installation by checking Help > About Notepad++ to confirm the version number is greater than 8.1
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6401 — 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-2023-6401 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