Lybbn Django-Vue-Lyadmin up to 3.2.12 JWT Signing settings.py SECRET_KEY hard-coded key
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 1.83 |
Summary
A vulnerability described as critical has been identified in Lybbn Django-Vue-Lyadmin up to 3.2.12. This affects an unknown function of the file backend/application/settings.py of the component JWT Signing. The manipulation of the argument SECRET_KEY results in hard-coded key. This vulnerability is identified as CVE-2026-105392. The attack can be executed remotely. Additionally, an exploit exists. The project maintainer explains: "The issue with this key is described in the documentation. Developers need to manually change their keys before deployment."
Details
A vulnerability classified as critical has been found in Lybbn Django-Vue-Lyadmin up to 3.2.12. Affected is an unknown code block of the file backend/application/settings.py of the component JWT Signing. The manipulation of the argument SECRET_KEY with an unknown input leads to a hard-coded key vulnerability. CWE is classifying the issue as CWE-321. The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered. This is going to have an impact on confidentiality, integrity, and availability.
The advisory is available at github.com. This vulnerability is traded as CVE-2026-105392. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details and a public exploit are known. This vulnerability is assigned to T1600.001 by the MITRE ATT&CK project.
The exploit is shared for download at github.com. It is declared as proof-of-concept. The project maintainer explains: "The issue with this key is described in the documentation. Developers need to manually change their keys before deployment."
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.9
VulDB Base Score: 7.3
VulDB Temp Score: 6.9
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Hard-coded keyCWE: CWE-321 / CWE-320
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
10/05/2026 Advisory disclosed10/05/2026 VulDB entry created
10/05/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-105392 (🔒)
GCVE (CVE): GCVE-0-2026-105392
GCVE (VulDB): GCVE-100-413586
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 10/05/2026 12:43Changes: 10/05/2026 12:43 (58)
Complete: 🔍
Submitter: HiiragiHaru
Cache ID: 216::103
Submit
Accepted
- Submit #982747: Lybbn Django-Vue-Lyadmin 6dcf930833d76d51780e12e024254a431e653f69 Hard-coded Cryptographic Key (by HiiragiHaru)
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.