dbcve.org
CenterApplication · Wacom

CVE-2024-12552

HIGH · 7.8 CVSS v3.1 Published 2024-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Wacom 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.exe. By creating a symbolic link, an attacker can abuse the service to create an arbitrary file. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of SYSTEM. Was ZDI-CAN-25359.

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 confidence

This is a local privilege escalation vulnerability in Wacom Center's WTabletServicePro.exe service. The flaw allows an attacker to create a symbolic link that the service will follow when creating files, enabling arbitrary file creation with SYSTEM privileges. By placing a symlink, a low-privileged attacker can escalate to SYSTEM context and execute arbitrary code.

MitigationUpdate Wacom Center to the latest version to obtain the vendor patch. If immediate patching is not feasible, consider disabling WTabletServicePro.exe if the tablet functionality is not required, or restrict file creation permissions for the service account.

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
CenterApplication
Affected:= 6.4.7.5003

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Wacom Center installation and version
    Open Programs and Features (appwiz.cpl) or check C:\Program Files\Wacom Center for the application. Look for Wacom Center in the installed programs list and note the version number shown.
    Affected if The installed version is exactly 6.4.7.5003 (note: only this exact version is affected; other versions may not be vulnerable).
  2. Locate WTabletServicePro.exe service
    Open Services (services.msc) and look for a service named WTabletServicePro, or check Task Manager for a process named WTabletServicePro.exe. Also check C:\Program Files\Tablet\WTabletServicePro.exe or similar paths.
    Affected if The service executable exists on the system (the vulnerability exists when this service runs).
  3. Determine if WTabletServicePro.exe is running
    Open Task Manager, go to the Services tab, or run 'sc query WTabletServicePro' or 'tasklist /FI "IMAGENAME eq WTabletServicePro.exe"' in Command Prompt.
    Affected if The service is currently running (the symlink attack requires the service to be active and creating files).
  4. Check permissions on Wacom service directories
    Right-click the folder containing WTabletServicePro.exe (commonly in C:\Program Files\Wacom or C:\Program Files\Tablet) and view Properties > Security. Check if standard users have 'Create symbolic links' privilege or Write/Modify permissions that would allow placing a symlink in service-accessible paths.
    Affected if Low-privileged users have permissions to create symbolic links in directories accessed by the Wacom service, or can write to locations where the service creates files.

You are affected if Wacom Center version 6.4.7.5003 is installed AND the WTabletServicePro.exe service is running, combined with permissions that allow a low-privileged user to place a symlink in a location the service uses for file creation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Wacom Center to the latest version to obtain the vendor patch. If immediate patching is not feasible, consider disabling WTabletServicePro.exe if the tablet functionality is not required, or restrict file creation permissions for the service account.

Fix this in Center Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12552 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-12552 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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