CVE-2024-9766
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 · uneditedWacom Center WTabletServicePro Link Following Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of Wacom Center. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within WTabletServicePro process. By creating a symbolic link, an attacker can abuse the service to create a file. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of SYSTEM. Was ZDI-CAN-24304.
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 confidenceWacom Center's WTabletServicePro service contains a symlink vulnerability allowing local privilege escalation. Attackers create a symbolic link that the service follows when creating a file, enabling arbitrary code execution as SYSTEM. The flaw requires low-privileged code execution as a prerequisite.
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< 6.4.7CVSS 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 Wacom Center installed versionOpen Windows Settings > Apps > Apps & Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*Wacom*"} | Select-Object DisplayName, DisplayVersion'Affected if DisplayVersion is less than 6.4.7 or version cannot be determined (may indicate vulnerable old installation)
-
Verify WTabletServicePro service presenceOpen Services console (services.msc) or run 'Get-Service WTabletServicePro' in PowerShellAffected if Service exists and is running on the system
-
Identify service-accessible directoriesRun 'sc qc WTabletServicePro' to find the binary path, then check the directory where the service executes from for write access by low-privileged usersAffected if Low-privileged users can create files in directories the service uses
-
Scan for unauthorized symlinks in service directoriesUse 'Get-ChildItem -Path <service_directory> -Recurse -LinkType SymbolicLink' to find any symlinks, or manually inspect directories for .symlink files or suspicious shortcutsAffected if Unexpected symbolic links exist in or near service-accessible directories
-
Check file creation permissions for standard usersUse icacls or PowerShell Get-Acl to verify write permissions on service directories for Users or Authenticated Users groupsAffected if Standard users have FILE_ADD_FILE or FILE_ADD_SUBDIRECTORY permissions on service directories
A system is affected if Wacom Center version is below 6.4.7 and the WTabletServicePro service runs with permissions that allow low-privileged users to create symlinks in service-accessible directories.
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 · scoped6.4.7
Apply vendor patch when available. Until then, restrict file creation permissions for the service account and monitor for unauthorized symlink creation in service-accessible directories.
Wacom Center version 6.4.7 or later
- Identify the current version of Wacom Center installed on the system
- Upgrade Wacom Center to version 6.4.7 or later
- Verify the upgrade was successful by checking the installed version
- Restart any Wacom-related services if prompted
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9766 — 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-2024-9766 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