# CVE-2023-1462: IDOR in Digikent

> Attackers can bypass authentication and abuse accounts in DigiKent by exploiting an Insecure Direct Object Reference vulnerability.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Mar 2023
- **Updated:** 1 Jun 2026
- **Also known as:** GHSA-jmf3-5xjh-86wj

## What is CVE-2023-1462?

CVE-2023-1462 is a high-severity missing authorization vulnerability in Vadi Corporate Information Systems DigiKent, published on 21 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Authorization Bypass Through User-Controlled Key vulnerability in Vadi Corporate Information Systems DigiKent allows Authentication Bypass, Authentication Abuse. This issue affects DigiKent: before 23.03.20.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 1 product.


Products: Vadi Digikent.

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

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

## Is CVE-2023-1462 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-1462 is a high-severity missing authorization vulnerability in Vadi Corporate Information Systems DigiKent, published on 21 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-1462 in the wild and no public exploit code.

Affected product: Vadi Corporate Information Systems DigiKent. 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-1462/ (Markdown: https://insights.sbomify.com/CVE-2023-1462/index.md)
```

## Sources

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

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