CVE-2026-8637
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 potential uncontrolled search path vulnerability was reported in the LanSchool Classic client application that could allow a local authenticated user to execute arbitrary code with elevated privileges.
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 confidenceThis is an uncontrolled search path vulnerability in LanSchool Classic client that allows a local authenticated user to execute arbitrary code with elevated privileges, likely through DLL hijacking or unquoted service path manipulation.
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
- 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.
-
Verify LanSchool Classic is installedCheck for LanSchool Classic installation by searching for the application in Program Files or Program Files (x86) directories, or look for the Lanschool.exe process running on the systemAffected if LanSchool Classic client is present on the system
-
Identify installed versionRight-click on Lanschool.exe in the installation directory, select Properties, and check the Version tab for the file version; alternatively, check Windows Registry under HKLM\SOFTWARE\LanSchool or HKLM\SOFTWARE\Wow6432Node\LanSchool for version informationAffected if Version cannot be determined or falls within an unpatched version range
-
Inspect application directory permissionsRight-click the LanSchool installation folder, select Properties, go to the Security tab, and check which users have Write or Modify permissions on the folder and its contentsAffected if Authenticated users or low-privilege users have Write access to the LanSchool installation directory or subdirectories
-
Check for unquoted service pathsOpen Command Prompt as Administrator and run: sc qc lanschool (or the actual service name if different), then inspect the BINARY_PATH_NAME for unquoted paths with spaces; also run: wmic service get name,displayname,pathname,startmode | findstr /i "lanschool"Affected if Service executable path contains spaces and is not enclosed in quotes
-
Audit for suspicious DLLs in application directoryList all DLL files in the LanSchool installation directory and check for any unexpected or recently added DLLs that could be used for hijacking; review the application directory for any executable files other than the main Lanschool.exeAffected if Unexpected DLL files or executables exist in the LanSchool installation folder that could be planted for DLL hijacking
The environment is affected if LanSchool Classic is installed, the installed version is unpatched, and writable directories or unquoted service paths exist that could allow an authenticated user to place malicious DLLs or executables 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 dataApply vendor patch when available; until then, restrict write access to application directories and monitor for suspicious executable placement.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8637 — 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-2026-8637 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