# CVE-2023-31181: WJJ Software - InnoKB Server, InnoKB/Console 2.2.1 - CWE-22: Path Traversal

> Attackers can exploit a path traversal vulnerability in InnoKB Server to read arbitrary files from the server.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 May 2023
- **Updated:** 29 Jan 2025
- **Also known as:** GHSA-f94g-p7rg-4254

## What is CVE-2023-31181?

CVE-2023-31181 is a high-severity path traversal vulnerability in  InnoKB Server, InnoKB/Console, published on 8 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WJJ Software - InnoKB Server, InnoKB/Console 2.2.1 - CWE-22: Path Traversal

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Wjjsoft Innokb.

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

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

## Is CVE-2023-31181 being exploited?

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

## Other vulnerabilities in  InnoKB Server, InnoKB/Console

- [CVE-2023-31180](https://insights.sbomify.com/CVE-2023-31180/): WJJ Software - InnoKB Server, InnoKB/Console 2.2.1 - Reflected cross-site scripting (RXSS) (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-31181 is a high-severity path traversal vulnerability in  InnoKB Server, InnoKB/Console, published on 8 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-31181 in the wild and no public exploit code.

Affected product:  InnoKB Server, InnoKB/Console. 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-31181/ (Markdown: https://insights.sbomify.com/CVE-2023-31181/index.md)
```

## Sources

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

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