Skip to main content
VulnerabilityPublished

CVE-2026-105392: Lybbn Django-Vue-Lyadmin · Use of Hard-coded Cryptographic Key

Affects Lybbn Django-Vue-LyadminSource CVE Database V5

0
Compare

Public exploit available · CVSS 6.9 Medium.

Data as of 19 Nov 2026, 20:25 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
LybbnDjango-Vue-LyadminAffected
  • 3.2.0 – 3.2.12
13 affected builds
Fixed in–
GitHublybbn/django-vue-lyadminpkg:github/lybbn/django-vue-lyadminOther threatsAffected
  • 3.2.0 – 3.2.12
13 affected builds
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:lybbn:django-vue-lyadmin:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Developers must manually change the hard-coded SECRET_KEY before deploying the application, as recommended by the project maintainer. Ensuring unique, securely generated keys for JWT signing is essential to mitigate this vulnerability.

Description

CVE-2026-105392 is a vulnerability in Lybbn Django-Vue-Lyadmin up to version 3.2.12 where a hard-coded cryptographic key is used in the JWT signing component. This issue arises from the SECRET_KEY argument in backend/application/settings.py. Remote exploitation is possible, and the exploit has been publicly disclosed. The project maintainer advises developers to manually change the keys before deployment to mitigate the risk.

References

Community reviews

Loading reviews…