CVE-2026-6610

liangliangyy DjangoBlog Setting settings.py hard-coded credentials

View on CVE.org
Published Apr 20, 2026 CVSS 4.0 · 6.3 Medium EPSS < 1% KEV · Not listed
Description
A vulnerability has been found in liangliangyy DjangoBlog up to 2.1.0.0. The impacted element is an unknown function of the file djangoblog/settings.py of the component Setting Handler. Such manipulation of the argument USER/PASSWORD leads to hard-coded credentials. The attack may be launched remotely. The attack requires a high level of complexity. The exploitability is regarded as difficult. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Analysis

AI-generated

Technical impact

A vulnerability exists in liangliangyy DjangoBlog where the settings.py file contains hard‑coded database credentials. This flaw allows an attacker capable of influencing the settings handler to overwrite or expose valid user and password values. If successfully exploited, the attacker could gain read or write access to the underlying database, compromising confidentiality and integrity of stored data.

Affected Systems

The issue affects versions of liangliangyy DjangoBlog up to 2.1.0.0. No other products or versions are listed as impacted.

Risk and Exploitability

The CVSS score of 6.3 indicates a medium severity risk. EPSS data is not available, and the vulnerability is not listed in the CISA KEV catalog, suggesting limited public exploitation so far. The description states that attack may be launched remotely and requires a high level of complexity, implying that successful exploitation would need sophisticated techniques and likely sufficient system access. Despite the moderate scoring, the presence of hard‑coded credentials remains a significant security concern for deployments of the affected DjangoBlog version.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade liangliangyy DjangoBlog to a version that no longer hard‑codes credentials or apply a local patch removing the credentials from settings.py.
  • Move database credentials out of source code by storing them in environment variables or a secure secrets manager and updating settings.py accordingly.
  • Disable DEBUG mode in production and set restrictive file permissions on settings.py to prevent unauthorized modifications.

Generated by OpenCVE AI on April 20, 2026 at 07:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}
Type Values Removed Values Added
First Time appeared Liangliangyy
Liangliangyy djangoblog
Vendors & Products Liangliangyy
Liangliangyy djangoblog
Type Values Removed Values Added
Description A vulnerability has been found in liangliangyy DjangoBlog up to 2.1.0.0. The impacted element is an unknown function of the file djangoblog/settings.py of the component Setting Handler. Such manipulation of the argument USER/PASSWORD leads to hard-coded credentials. The attack may be launched remotely. The attack requires a high level of complexity. The exploitability is regarded as difficult. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Title liangliangyy DjangoBlog Setting settings.py hard-coded credentials
Weaknesses CWE-259
CWE-798
References
Metrics cvssV2_0

{'score': 2.6, 'vector': 'AV:N/AC:H/Au:N/C:P/I:N/A:N/E:POC/RL:ND/RC:UR'}

cvssV3_0

{'score': 3.7, 'vector': 'CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N/E:P/RL:X/RC:R'}

cvssV3_1

{'score': 3.7, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N/E:P/RL:X/RC:R'}

cvssV4_0

{'score': 6.3, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P'}
Weaknesses
  • CWE-259

    Use of Hard-coded Password

  • CWE-798

    Use of Hard-coded Credentials

Sources

Status
PUBLISHED
Assigner
VulDB
Published
Updated
Apr 20, 2026, 4:03 PM
Reserved
Apr 19, 2026, 4:06 PM

View source JSON

Updated
Apr 20, 2026, 4:02 PM

JSON

Status
Deferred
Published
Apr 20, 2026, 6:16 AM
Modified
Oct 26, 2026, 9:10 PM

View source JSON

No data.

Updated
Apr 20, 2026, 2:58 PM

JSON