# CVE-2023-31468: Privilege escalation in n/a

> Weak folder permissions allow attackers to insert malicious files that execute with SYSTEM privileges, requiring an upgrade to the fixed version.

- **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:** 11 Sep 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-m9q4-fmg6-m8r5

## What is CVE-2023-31468?

CVE-2023-31468 is a high-severity vulnerability in n/a, published on 11 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in Inosoft VisiWin 7 through 2022-2.1 (Runtime RT7.3 RC3 20221209.5). The "%PROGRAMFILES(X86)%\INOSOFT GmbH" folder has weak permissions for Everyone, allowing an attacker to insert a Trojan horse file that runs as SYSTEM. 2024-1 is a fixed version.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Inosoft Visiwin 7.

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

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

## Is CVE-2023-31468 being exploited?

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

Public exploit code:

- Inosoft VisiWin 7 2022-2.1 - Insecure Folders Permissions (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-31468 is a high-severity vulnerability in n/a, published on 11 Sep 2023. 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-31468 exists.

Affected product: n/a. 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-31468/ (Markdown: https://insights.sbomify.com/CVE-2023-31468/index.md)
```

## Sources

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

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