dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2024-12903

HIGH · 7.8 CVSS v3.1 Published 2024-12-23
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
Incorrect default permissions vulnerability in Evoko Home, affecting version 2.4.2 to 2.7.4. A non-admin user could exploit weak file and folder permissions to escalate privileges, execute arbitrary code and maintain persistence on the compromised machine. It has been identified that full control permissions exist on the ‘Everyone’ group (i.e. any user who has local access to the operating system regardless of their 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 confidence

Evoko Home versions 2.4.2 through 2.7.4 ship with overly permissive file and folder permissions, granting the 'Everyone' group Full Control access. This allows any local user on the Windows system to read, write, modify, or delete application files, enabling privilege escalation from low-privileged accounts to SYSTEM, arbitrary code execution, and persistent malware installation.

MitigationRestrict file and folder permissions by removing the 'Everyone' group and implementing principle of least privilege with appropriate user-specific or group-based ACLs, then verify Evoko Home functionality after the permission changes.

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 checks

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

  1. Locate Evoko Home installation directory
    Search for 'Evoko Home' folder in typical installation locations such as C:\Program Files\Evoko Home or C:\Program Files (x86)\Evoko Home, or use PowerShell: Get-ChildItem -Path 'C:\Program Files','C:\Program Files (x86)' -Recurse -Directory -ErrorAction SilentlyContinue | Where-Object {$_.Name -like '*Evoko*'}.
    Affected if The Evoko Home directory exists on the system.
  2. Identify installed version
    Right-click the Evoko Home executable (such as EvokoHome.exe) in the installation folder, select Properties, and check the File Version on the Details tab. Alternatively, run: (Get-Item 'C:\Program Files\Evoko Home\EvokoHome.exe').VersionInfo.FileVersion.
    Affected if The version falls within 2.4.2 through 2.7.4 inclusive.
  3. Verify Everyone group permissions on installation folder
    Right-click the Evoko Home installation folder, select Properties, go to the Security tab, and check the Group or user names list for 'Everyone'. Click on Everyone and verify that the Allow column shows Full control (or all permissions). Alternatively, run in PowerShell: Get-Acl 'C:\Program Files\Evoko Home' | Select-Object -ExpandProperty Access | Where-Object {$_.IdentityReference -like '*Everyone*'}.
    Affected if The 'Everyone' group is present and granted Full Control or Modify permissions on the installation folder or its subfolders.
  4. Verify Everyone group permissions on application data folders
    Check common application data locations such as %AppData%\Evoko Home and %LocalAppData%\Evoko Home for the same overly permissive 'Everyone' group permissions using the Security tab or Get-Acl cmdlet.
    Affected if The 'Everyone' group has Full Control or Modify permissions on any Evoko Home data folder.

A system is affected if Evoko Home version 2.4.2 through 2.7.4 is installed AND the installation folder or its data directories grant the 'Everyone' group Full Control or Modify permissions.

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

Restrict file and folder permissions by removing the 'Everyone' group and implementing principle of least privilege with appropriate user-specific or group-based ACLs, then verify Evoko Home functionality after the permission changes.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12903 — 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-12903 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