# CVE-2023-53947: OCS Inventory NG 2.3.0.0 Unquoted Service Path Privilege Escalation

> Local attackers can escalate privileges to system level by placing a malicious executable in the unquoted service path of OCS Inventory NG.

- **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:** 19 Dec 2025
- **Updated:** 14 May 2026
- **Also known as:** GHSA-qhww-qrj4-8v34

## What is CVE-2023-53947?

CVE-2023-53947 is a high-severity vulnerability in oscinventory OCS Inventory NG, published on 19 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

OCS Inventory NG 2.3.0.0 contains an unquoted service path vulnerability that allows local attackers to escalate privileges to system level. Attackers can place a malicious executable in the unquoted service path and trigger the service restart to execute code with elevated system privileges.

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

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


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

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

## Is CVE-2023-53947 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-53947 is a high-severity vulnerability in oscinventory OCS Inventory NG, published on 19 Dec 2025. 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-2023-53947 exists.

Affected product: oscinventory OCS Inventory NG. 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-53947/ (Markdown: https://insights.sbomify.com/CVE-2023-53947/index.md)
```

## Sources

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

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