CVE-2026-6610Network attack vector

Credential disclosure via hard-coded database fallbacks

Published Apr 20, 2026 · Updated Apr 20, 2026

Hard-coded credentials in DjangoBlog 2.1.0 allow remote attackers to obtain sensitive deployment details through exposed debug pages. In djangoblog/settings.py, absent DJANGO_MYSQL_USER or DJANGO_MYSQL_PASSWORD environment variables fall back to root/root while DEBUG defaults to enabled. Exposure requires a network-reachable deployment that omits those variables and serves a triggering error; the bounded impact is disclosure of stack traces, settings, and local variables, plus guessable host-local database credentials.

CVSS severity3.7
Low
EPSS probability0.27%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Hard-coded credentials in DjangoBlog 2.1.0 allow remote attackers to obtain sensitive deployment details through exposed debug pages. In djangoblog/settings.py, absent DJANGO_MYSQL_USER or DJANGO_MYSQL_PASSWORD environment variables fall back to root/root while DEBUG defaults to enabled. Exposure requires a network-reachable deployment that omits those variables and serves a triggering error; the bounded impact is disclosure of stack traces, settings, and local variables, plus guessable host-local database credentials.

The record

CVE
CVE-2026-6610
Published
Apr 20, 2026
Updated
Apr 20, 2026
Vendor
liangliangyy
Product
DjangoBlog
Classifications
CWE-798, T1552.001
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Apr 20, 2026CVE publishedPublication date reported by the CVE source.
  2. Apr 20, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=2.1.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

liangliangyy · DjangoBlogversion=2.1.0

Published CVSS scores

2.6TenableAV:N/AC:H/Au:N/C:P/I:N/A:N
6.3TenableCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
3.7TenableCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-798Use of Hard-coded Credentials
T1552.001Unsecured Credentials: Credentials In Files

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo