# CVE-2023-5921: Function Bypass in Geodi

> Attackers can bypass intended functionality workflows in DECE Software Geodi due to improper enforcement of behavioral logic.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A: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:** 22 Nov 2023
- **Updated:** 20 May 2026
- **Also known as:** GHSA-qm72-9j6p-39q3

## What is CVE-2023-5921?

CVE-2023-5921 is a high-severity vulnerability in DECE Software Geodi, published on 22 Nov 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper Enforcement of Behavioral Workflow vulnerability in DECE Software Geodi allows Functionality Bypass.

This issue affects Geodi: before 8.0.0.27396.

Weakness: CWE-841 (Improper Enforcement of Behavioral Workflow)

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

It affects 1 product.


Products: Decesoftware Geodi.

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

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

## Is CVE-2023-5921 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-5921 is a high-severity vulnerability in DECE Software Geodi, published on 22 Nov 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-5921 in the wild and no public exploit code.

Affected product: DECE Software Geodi. 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-5921/ (Markdown: https://insights.sbomify.com/CVE-2023-5921/index.md)
```

## Sources

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

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