# CVE-2021-47974: VX Search 13.5.28 Unquoted Service Path Privilege Escalation

> Local attackers can escalate privileges to LocalSystem by placing malicious executables in unquoted service path directories.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 16 May 2026
- **Updated:** 18 May 2026
- **Also known as:** GHSA-2jpw-mvcx-5wqh

## What is CVE-2021-47974?

CVE-2021-47974 is a high-severity vulnerability in Vxsearch VX Search, published on 16 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

VX Search 13.5.28 contains an unquoted service path vulnerability in both VX Search Server and VX Search Enterprise services that allows local attackers to escalate privileges. Attackers can place malicious executables in unquoted path directories like C:\Program Files\VX Search to execute arbitrary code with LocalSystem privileges when services restart.

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

## Which versions are affected by CVE-2021-47974?


## How do I fix CVE-2021-47974?

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

## Is CVE-2021-47974 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-47974 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-47974 and fix it if it is affected.

What it is: CVE-2021-47974 is a high-severity vulnerability in Vxsearch VX Search, published on 16 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-47974 exists.

Affected product: Vxsearch VX Search. 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-2021-47974/ (Markdown: https://insights.sbomify.com/CVE-2021-47974/index.md)
```

## Sources

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

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