Insecure JWT Signing Configuration in Lybbn Django-Vue-Lyadmin
CVE-2026-105392

6.9MEDIUM

Key Information:

Vendor

Lybbn

Status
Django-vue-lyadmin
Vendor
CVE Published:
5 October 2026

Badges

👾 Exploit Exists🟡 Public PoC

What is CVE-2026-105392?

A security flaw exists in the JWT Signing configuration of Lybbn Django-Vue-Lyadmin up to version 3.2.12, where the SECRET_KEY argument is hard-coded within the backend/application/settings.py file. This weakness allows for potential remote exploitation, as the hard-coded key can be manipulated. Developers are advised to change their keys manually before deploying the application to mitigate this risk, as noted by the project maintainer.

Affected Version(s)

Django-Vue-Lyadmin 3.2.0

Django-Vue-Lyadmin 3.2.1

Django-Vue-Lyadmin 3.2.2

Exploit Proof of Concept (PoC)

PoC code is written by security researchers to demonstrate the vulnerability can be exploited. PoC code is also a key component for weaponization which could lead to ransomware.

CVE-2026-105392 - Proof of Concept

References

https://vuldb.com/vuln/413586
vdb-entrytechnical-description
https://vuldb.com/vuln/413586/cti
signaturepermissions-required
https://vuldb.com/cve/CVE-2026-105392
third-party-advisory

CVSS V4

Score:
6.9
Severity:
MEDIUM
Confidentiality:
Low
Integrity:
Low
Availability:
Low
Attack Vector:
Network
Attack Complexity:
Low
Attack Required:
None
Privileges Required:
Undefined
User Interaction:
None

Timeline

  • 🟡

    Public PoC available

  • 👾

    Exploit known to exist

  • Vulnerability published

  • Vulnerability Reserved

Credit

HiiragiHaru (VulDB User)
VulDB CNA Team
.