dbcve.org
DigikentApplication · Vadi

CVE-2023-1462

HIGH · 8.8 CVSS v3.1 Published 2023-03-21
Fix available
A fix is available. Upgrade to 23.03.20 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

An authorization bypass vulnerability in DigiKent allows attackers to manipulate user-controlled keys (likely API parameters or identifiers) to bypass authentication mechanisms. This enables unauthorized access to restricted resources or functions by altering values that the application uses to determine user identity or privileges.

MitigationUpgrade DigiKent to version 23.03.20 or later to obtain the vendor patch that addresses this authorization bypass vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DigikentApplication
Affected:< 23.03.20

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify DigiKent installation
    Check for Vadi Digikent web application in your environment by reviewing installed software, web server logs, or consulting your system inventory for applications named 'Digikent', 'DigiKent', or 'Vadi Digikent'
    Affected if Vadi Digikent is not found in your environment (not affected)
  2. Determine installed version
    Locate the DigiKent version information - typically found in the application admin panel under 'About' or 'System Information', in the software's changelog/readme files, or by checking the application's footer/branding area for version display
    Affected if Unable to determine version or version is < 23.03.20 (potentially affected)
  3. Compare version against affected range
    If version is identified, compare the numeric version against 23.03.20 - versions below 23.03.20 (e.g., 23.02.x, 22.x.x, etc.) are within the affected range
    Affected if Installed version is any build prior to 23.03.20
  4. Inspect API parameter handling
    Review application logs and HTTP traffic for API endpoints that accept user-controlled identifiers (such as user IDs, session tokens, or record IDs in URL parameters or request bodies) - look for patterns where these parameters could be manipulated
    Affected if API endpoints with modifiable user-controlled keys are accessible without additional authentication checks

Your environment is affected if Vadi Digikent is installed and the version is below 23.03.20, especially if the application exposes API endpoints accepting user-controlled parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 23.03.20 or later
Fixed in 23.03.20
Interim mitigation

Upgrade DigiKent to version 23.03.20 or later to obtain the vendor patch that addresses this authorization bypass vulnerability.

Recommended fix Moderate confidence

Digikent version 23.03.20 or later

  1. Obtain the Digikent version 23.03.20 or later from the vendor (Vadi Corporate Information Systems)
  2. Review release notes or changelog for version 23.03.20 to understand changes
  3. Create a backup of the current Digikent installation and database
  4. Test the upgrade in a staging environment before production deployment
  5. Deploy version 23.03.20 or later to production environment
  6. Verify the authorization bypass vulnerability is resolved by testing access controls

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Digikent Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA6.0 h
32.0 hours of engineering $5,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,024.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-1462 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-1462 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data