---
id: CVE-2026-105392
title: A vulnerability has been found in Lybbn Django-Vue-Lyadmin up to 3.2.12
summary: >-
  A vulnerability has been found in Lybbn Django-Vue-Lyadmin up to 3.2.12. The
  impacted element is an unknown function of the file
  backend/application/settings.py of the component JWT Signing. The manipulation
  of the argument SECRET_KEY le…
severity: high
cvss: 7.3
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L'
cwe:
  - CWE-320
  - CWE-321
vendor: Lybbn
product: Django-Vue-Lyadmin
affected:
  - Django-Vue-Lyadmin 3.2.0
  - Django-Vue-Lyadmin 3.2.1
  - Django-Vue-Lyadmin 3.2.2
  - Django-Vue-Lyadmin 3.2.3
  - Django-Vue-Lyadmin 3.2.4
  - Django-Vue-Lyadmin 3.2.5
  - Django-Vue-Lyadmin 3.2.6
  - Django-Vue-Lyadmin 3.2.7
  - Django-Vue-Lyadmin 3.2.8
  - Django-Vue-Lyadmin 3.2.9
  - Django-Vue-Lyadmin 3.2.10
  - Django-Vue-Lyadmin 3.2.11
  - Django-Vue-Lyadmin 3.2.12
published: '2026-10-05'
updated: '2026-10-05'
sourceUpdated: '2026-10-05T20:17:10.827'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-105392'
references:
  - url: 'https://github.com/lybbn/django-vue-lyadmin/'
    label: cna@vuldb.com
  - url: 'https://github.com/lybbn/django-vue-lyadmin/issues/3'
    label: cna@vuldb.com
  - url: 'https://vuldb.com/cve/CVE-2026-105392'
    label: cna@vuldb.com
  - url: 'https://vuldb.com/submit/982747'
    label: cna@vuldb.com
  - url: 'https://vuldb.com/vuln/413586'
    label: cna@vuldb.com
  - url: 'https://vuldb.com/vuln/413586/cti'
    label: cna@vuldb.com
tags:
  - nvd
  - cve.org
ingestedAt: '2026-10-05T20:32:56.646Z'
---

## Overview

A vulnerability has been found in Lybbn Django-Vue-Lyadmin up to 3.2.12. The impacted element is an unknown function of the file backend/application/settings.py of the component JWT Signing. The manipulation of the argument SECRET_KEY leads to use of hard-coded cryptographic key
 . Remote exploitation of the attack is possible. The exploit has been disclosed to the public and may be used. The project maintainer explains: "The issue with this key is described in the documentation. Developers need to manually change their keys before deployment."

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.