Quest Foglight for Databases runScript Incorrect Authorization Remote Code Execution Vulnerability
Affects Quest Foglight for Databases, but the checked facts list no affected version ranges. Fixed in Foglight 8.3.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in Foglight 8.3
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected product is Quest Foglight for Databases; the flaw is in the runScript function.
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity8.8/10CVSS 8.8
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
CVE-2026-92191 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.8 (high) and affects Foglight for Databases; fixed in Foglight 8.3.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in Foglight 8.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Quest Foglight for Databases is affected by this vulnerability, which lets a remote attacker who has valid login credentials run arbitrary code on the server with SYSTEM-level privileges. The flaw stems from missing authorization checks in the runScript function, allowing access to functionality that should be restricted.
Read the original description
Quest Foglight for Databases runScript Incorrect Authorization Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Quest Foglight for Databases. Authentication is required to exploit this vulnerability. The specific flaw exists within the runScript function. The issue results from incorrect authorization prior to allowing access to functionality. An attacker can leverage this vulnerability to execute code in the context of SYSTEM. Was ZDI-CAN-29192.
What to do
Check whether your setup matches what the bug needs.
Affected product is Quest Foglight for Databases; the flaw is in the runScript function.Upgrade to a fixed version: Foglight 8.3.
Timeline
- CVE published1 day
- First seen by cve.now
Affected versions
- Quest Foglight for Databases
8.2.0
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-92191
Is CVE-2026-92191 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The flaw is in the runScript function of Quest Foglight for Databases. A remote attacker can use it to run arbitrary code in the context of SYSTEM.Source: zerodayinitiative.com
Which versions are affected by CVE-2026-92191?
Foglight for Databases: version 8.2.0.Source: cve.now feed data
Am I affected, and how do I check?
The checked facts name Quest Foglight for Databases but give no affected version ranges, so the exact affected versions are not confirmed. Check the installed Foglight version against the vendor advisory to see whether it falls in the affected range.Source: zerodayinitiative.com
How do I fix CVE-2026-92191?
Upgrade Foglight to 8.3, the release that fixes this flaw. The checked facts list no workaround.Source: zerodayinitiative.com