LiveActive security incident?Get immediate response
CVE Record

CVE-2023-5921: Function Bypass in Geodi

Improper Enforcement of Behavioral Workflow vulnerability in DECE Software Geodi allows Functionality Bypass. This issue affects Geodi: before 8.0.0.27396.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-5921 is a workflow enforcement flaw in DECE Software Geodi. A low-privileged local user could bypass intended functionality controls, potentially exposing or altering sensitive information. It is high severity, but the sources do not show active exploitation or a remote unauthenticated attack path.

Executive priority

Prioritize remediation where Geodi handles sensitive or regulated information. This is a high-severity internal exposure, but not an emergency internet-wide threat based on current cited evidence.

Technical view

The CVE describes CWE-841, Improper Enforcement of Behavioral Workflow, in Geodi before 8.0.0.27396. CVSS 3.1 is 7.1: local attack vector, low complexity, low privileges, no user interaction, high confidentiality and integrity impact, and no availability impact.

Likely exposure

Exposure appears limited to organizations running DECE Software Geodi versions before 8.0.0.27396. The CVSS vector indicates a local, low-privileged attacker context, not direct unauthenticated remote exploitation based on provided sources.

Exploitation context

CISA KEV is false in the provided data, and no cited source states active exploitation. The issue is still important because successful bypass could affect sensitive data confidentiality and integrity inside an environment where Geodi is used.

Researcher notes

Public details are sparse. The CVE record names Geodi before 8.0.0.27396, but affected-version metadata is minimal and one government reference is marked broken in the bundle. Avoid assuming exploit availability or broader product impact.

Mitigation direction

  • Identify all Geodi installations and current versions.
  • Update Geodi to 8.0.0.27396 or later if vendor guidance confirms availability.
  • Restrict local and low-privileged access to Geodi systems.
  • Review Geodi permission models and workflow controls.
  • Monitor for unusual data access or workflow bypass indicators.

Validation and detection

  • Confirm installed Geodi version is not earlier than 8.0.0.27396.
  • Check vendor or government advisory for final remediation instructions.
  • Validate that unauthorized low-privileged users cannot access restricted functions.
  • Review logs for suspicious access to sensitive Geodi-managed data.
  • Document compensating controls where immediate upgrade is not possible.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-841: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-5921 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N1.85.2TR-CERT

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2023-5921Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
DECE SoftwareGeodi0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-841 · source CWE mapping

Improper Enforcement of Behavioral Workflow

Improper Enforcement of Behavioral Workflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.