Skip to main content
Menu
CVEs

Asp.Net-Core-Inventory-Order-Management-System auth bypass via hard-coded JWT signing key

Affects go2ismail's Asp.Net-Core-Inventory-Order-Management-System before 10.20261109 when run with the hard-coded JWT signing key from appsettings.json, including the default demo mode. Fixed in 10.20261109.

CVE-2026-125383EUVD-2026-120546Published November 9, 2026, updated

9.3CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 10.20261109
Who is exposed
Not reported

Summary

Written by a model

INDOTALENT WHMS (Asp.Net-Core-Inventory-Order-Management-System) before 10.20261109 contains an authentication bypass vulnerability caused by a hard-coded JWT signing key, issuer and audience in appsettings.json. Unauthenticated remote attackers can forge tokens for any user ID and role that the Tokens/DI.cs validator trusts, gaining administrator access to the entire API.

Who should check

Teams running go2ismail's Asp.Net-Core-Inventory-Order-Management-System (INDOTALENT WHMS) before 10.20261109, including demo deployments

Not fixed by: Leaving IsDemoVersion=true in production keeps the demo key valid.

“A fresh clone runs in demo mode.”

github.com

What to do

Upgrade to a fixed version: 10.20261109.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-125383 (INDOTALENT WHMS before 10.20261109 Hard-Coded JWT Signing Key Authentication Bypass), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-125383 (entry last updated 2026-11-12):
Affected:
- go2ismail Asp.Net-Core-Inventory-Order-Management-System: fixed in 10.20261109
Fixed versions: 10.20261109.
Conditions (all must be true for the bug to be hit):
- Runs the product with the hard-coded JWT signing key, issuer and audience from appsettings.json (source: https://www.vulncheck.com/advisories/indotalent-whms-before-10.20261109-hard-coded-jwt-signing-key-authentication-bypass)
- Demo mode is enabled, the default setting in the affected code (source: https://github.com/go2ismail/Asp.Net-Core-Inventory-Order-Management-System)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-125383 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125383 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/go2ismail/Asp.Net-Core-Inventory-Order-Management-System/commit/65609b5b88cb4f156e8164f33b8db8c63f5c125b
- https://github.com/go2ismail/Asp.Net-Core-Inventory-Order-Management-System/commit/ded7d8a9457c780dfd4f5ea74d7e72111fafaea6
- https://github.com/go2ismail/Asp.Net-Core-Inventory-Order-Management-System/issues/48
- https://github.com/go2ismail/Asp.Net-Core-Inventory-Order-Management-System
- https://github.com/go2ismail/Asp.Net-Core-Inventory-Order-Management-System/blob/v9.20250118/Presentation/ASPNET/appsettings.json#L38-L44
- https://github.com/go2ismail/Asp.Net-Core-Inventory-Order-Management-System/releases/tag/v10.20261109
- https://www.vulncheck.com/advisories/indotalent-whms-before-10.20261109-hard-coded-jwt-signing-key-authentication-bypass
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-125383
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-125383"}.

Affected versions

cve.now Index

30of 100 · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.3, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 35 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now1 day
  3. Posted on X by cve.now2 days
  4. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: total

  5. Record last updated

Public exploit activity

100%0Posted on X by cve.nowNov 9Nov 22
  • EPSS: 0.83%
  • Posted on X by cve.now Nov 10

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Evidence 9

Questions about CVE-2026-125383

Is CVE-2026-125383 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The product signs its login tokens with a JWT signing key, issuer and audience that are hard-coded in appsettings.json. Anyone who knows these values can forge tokens for any user ID and role, gaining administrator access to the entire API.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-125383?

Asp.Net-Core-Inventory-Order-Management-System: before 10.20261109.

Source: cve.now feed data

Am I affected, and how do I check?

All versions before 10.20261109 are affected when they run with the hard-coded JWT signing key, issuer and audience from appsettings.json. A fresh clone runs in demo mode, which is the default setting in the affected code. To check, look at the JWT signing key, issuer and audience values in appsettings.json and at the demo mode setting.

Source: vulncheck.com, github.com

How do I fix CVE-2026-125383?

Upgrade to version 10.20261109 or later, which is the listed fixed version. No vendor patch ids are named.

Source: vulncheck.com, github.com

No corrections so far. Something wrong on this page? Report an error.