INDOTALENT WHMS before 10.20261109 Hard-Coded JWT Signing Key Authentication Bypass
Affects go2ismail's Asp.Net-Core-Inventory-Order-Management-System (INDOTALENT WHMS) before 10.20261109, where the JWT signing key, issuer and audience are hard-coded in appsettings.json. Fixed in 10.20261109.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 10.20261109
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 10.20261109.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.3/10CVSS 9.3
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 10.20261109.
Timeline
- CVE published
- First seen by cve.now1 day
- Posted on X by cve.now
Affected versions
- go2ismail Asp.Net-Core-Inventory-Order-Management-System
fixed in 10.20261109
Evidence 7
- Patch
- Patch
- Report
- Repository
- Repository
Show all 7 sourcesShow fewer sources
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
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 JWT signing key, issuer and audience are hard-coded in appsettings.json, so an unauthenticated attacker can forge tokens for any user ID and role. That gives administrator access to the entire API.Source: vulncheck.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?
Product versions before 10.20261109 are in the affected range. To check a deployment, look at the installed version and whether appsettings.json contains the hard-coded JWT signing key, issuer and audience.Source: vulncheck.com
How do I fix CVE-2026-125383?
Upgrade to version 10.20261109, which is the listed fixed version and is covered by the v10.20261109 release notes.Source: vulncheck.com