CVE-2026-23703
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 · uneditedThe installer of FinalCode Client provided by Digital Arts Inc. contains an incorrect default permissions vulnerability. A non-administrative user may execute arbitrary code with SYSTEM privilege.
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 confidenceThe FinalCode Client installer from Digital Arts Inc. sets overly permissive file or folder permissions during installation. This allows non-privileged users to modify executable files, services, or configurations that subsequently run with SYSTEM-level privileges, enabling local privilege escalation.
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.0/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.
-
Identify FinalCode Client installationSearch for FinalCode installation directory - typically in Program Files or Program Files (x86). Check registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for FinalCode entry, or look for service named 'FinalCode' using sc query or Get-Service in PowerShell.Affected if FinalCode Client is installed on the system.
-
Locate installation directory permissionsRight-click the FinalCode installation folder, go to Properties > Security tab. Review the permissions for Users and Everyone groups. Alternatively, use icacls.exe: icacls "C:\Path\To\FinalCode" to list all permission entries.Affected if Users group or non-privileged accounts have Write or Full Control permissions on the installation directory.
-
Check executable file permissionsRun icacls.exe on .exe files in the FinalCode installation directory: icacls "C:\Path\To\FinalCode\*.exe" | findstr /i "Users Everyone" . Look for any executable where Users group has Modify or Full Control rights.Affected if Any executable in the FinalCode directory is writable by non-privileged users.
-
Identify FinalCode servicesRun sc queryex type= service to list all services, or use Get-Service in PowerShell. Filter for services with 'FinalCode' in the name. Then run sc qc <servicename> to get the binary path.Affected if A FinalCode service runs with SYSTEM or elevated privileges and its executable is located in a writable directory.
-
Check configuration file permissionsExamine config files (.ini, .xml, .conf) in the FinalCode directory using icacls. Run: icacls "C:\Path\To\FinalCode\*" /t | findstr /i "Users Everyone" . Look for any configuration file writable by Users group.Affected if Configuration files in the FinalCode directory are writable by non-privileged users, allowing modification of service behavior.
A user is affected if FinalCode Client is installed and the installation directory or its contents grant Write or Modify permissions to non-privileged users (Users group, standard users), enabling those users to replace executables or configs that run with SYSTEM privileges.
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 or reinstall with corrected permissions; audit and restrict write access on FinalCode installation directories to administrative users only.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23703 — 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-23703 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