dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2025-47422

HIGH · 7.5 CVSS v3.1 Published 2025-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Advanced Installer before 22.6 has an uncontrolled search path element local privilege escalation vulnerability. When running as SYSTEM in certain configurations, Advanced Installer looks in standard-user writable locations for non-existent binaries and executes them as SYSTEM. A low-privileged attacker can place a malicious binary in a targeted folder; when the installer is executed, the attacker achieves arbitrary SYSTEM code execution.

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

Advanced Installer before version 22.6 contains an uncontrolled search path vulnerability where the application running with SYSTEM privileges searches for binaries in user-writable directories. A low-privilege attacker can place a malicious executable in one of these search paths, which Advanced Installer will then execute with SYSTEM-level privileges, achieving arbitrary code execution.

MitigationUpgrade Advanced Installer to version 22.6 or later. As a compensating control, ensure standard user accounts do not have write access to directories in the application's search path and avoid running installers with elevated privileges unless necessary.

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 installed Advanced Installer version
    Locate Advanced Installer on the system (commonly in Program Files or Program Files (x86)) and check the version property of the executable, or query via Windows registry under HKLM\SOFTWARE\Caphyon\Advanced Installer (or HKLM\SOFTWARE\WOW6432Node\Caphyon\Advanced Installer) for the InstallPath and version values
    Affected if The installed version is any release earlier than version 22.6 (e.g., 22.5, 22.4, earlier)
  2. Determine if Advanced Installer runs with elevated privileges
    Observe the process execution context when Advanced Installer is launched; check whether it runs under the SYSTEM account, as administrator, or with elevated token via Task Manager or process audit logs
    Affected if Advanced Installer executes with SYSTEM or administrator-level privileges while searching for binaries in directories that non-privileged users can modify
  3. Identify directories in Advanced Installer's binary search path
    Examine the application's search path configuration by reviewing its executable properties, associated configuration files, or by monitoring which directories it queries when launching external binaries during installation workflows
    Affected if Any user-writable directory (such as user profile folders, temp directories, or network shares) is included in the search path that Advanced Installer uses when resolving executable dependencies

A system is affected if Advanced Installer version 22.5 or earlier is installed, runs with elevated (SYSTEM or administrator) privileges, and has user-writable directories in its binary search path, allowing a low-privilege attacker to inject malicious executables for privilege escalation.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Advanced Installer to version 22.6 or later. As a compensating control, ensure standard user accounts do not have write access to directories in the application's search path and avoid running installers with elevated privileges unless necessary.

Recommended fix High confidence

Advanced Installer 22.6 or later

  1. Back up your current Advanced Installer installation and any projects/configuration files.
  2. Navigate to the official Advanced Installer website (www.advancedinstaller.com) and download version 22.6 or later.
  3. Run the installer and complete the upgrade following standard installation procedures.
  4. Verify the installation completed successfully by checking the installed version number.
  5. Test that your existing projects open and function correctly in the upgraded version.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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