cve.bz

CVE-2026-125383 INDOTALENT WHMS before 10.20261109 Hard-Coded JWT Signing Key Authentication Bypass

9.3 criticalEPSS 0.8%

Critical (9.3) in go2ismail asp.net-core-inventory-order-management-system. EPSS 0.8% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

9.3 critical
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.8% estimated probability of exploitation activity in the next 30 days; 58th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-11-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-321 Use of Hard-coded Cryptographic Key
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
Assigned by
VulnCheck (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-125383 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-125383?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-125383?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-125383 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-125383

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-125383](https://cve.bz/cve/badge/CVE-2026-125383.svg)](https://cve.bz/cve/CVE-2026-125383)

HTML:

<a href="https://cve.bz/cve/CVE-2026-125383"><img src="https://cve.bz/cve/badge/CVE-2026-125383.svg" alt="CVE-2026-125383"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
go2ismail Asp.Net-Core-Inventory-Order-Management-Systembefore 10.20261109

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON