# CVE-2023-4991: NextBX QWAlerter QWAlerter.exe unquoted search path

> Local attackers can exploit an unquoted search path in QWAlerter.exe to execute arbitrary code with elevated privileges.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2023
- **Updated:** 25 Sep 2024
- **Also known as:** GHSA-wvxq-988m-ccxf

## What is CVE-2023-4991?

CVE-2023-4991 is a high-severity vulnerability in NextBX QWAlerter, published on 15 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in NextBX QWAlerter 4.50. It has been rated as critical. Affected by this issue is some unknown functionality of the file QWAlerter.exe. The manipulation leads to unquoted search path. It is possible to launch the attack on the local host. The identifier of this vulnerability is VDB-239804. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-428 (Unquoted Search Path or Element)

## Which versions are affected by CVE-2023-4991?

It affects 1 product.


Products: Quescom Nextbx Qwalerter.

## How do I fix CVE-2023-4991?

No fix has been published for CVE-2023-4991 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-4991 being exploited?

There is no known exploitation of CVE-2023-4991 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-4991 and fix it if it is affected.

What it is: CVE-2023-4991 is a high-severity vulnerability in NextBX QWAlerter, published on 15 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-4991 in the wild and no public exploit code.

Affected product: NextBX QWAlerter. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-4991/ (Markdown: https://insights.sbomify.com/CVE-2023-4991/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-4991
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-4991
- OSV: https://osv.dev/vulnerability/CVE-2023-4991

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-4991/
Summaries are generated and may contain mistakes; the official description above is the record.