{"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-06","sourceUpdated":"2026-10-06T18:16:45.200","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","exploit-available"],"exploitAvailable":true,"ssvc":{"exploitation":"poc","automatable":"yes","technicalImpact":"partial","timestamp":"2026-10-06T17:20:40.726914Z"},"ingestedAt":"2026-10-05T20:32:56.646Z","epss":0.00288,"epssPercentile":0.21234,"slug":"CVE-2026-105392","body":"## Overview\n\nA 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\r . 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.\"\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"midnight","depthScore":52,"depthScoreParts":{"impact":40.2,"likelihood":0.1,"exploitation":12,"ransomware":0},"changes":[{"seq":216668,"id":"CVE-2026-105392","ts":1791310396494,"field":"exploit_available","old":"false","new":"true"}]}