liangliangyy DjangoBlog up to 2.1.0.0 Setting djangoblog/settings.py USER/PASSWORD hard-coded credentials

Summaryinfo

A vulnerability classified as critical has been found in liangliangyy DjangoBlog up to 2.1.0.0. This affects an unknown function of the file djangoblog/settings.py of the component Setting Handler. Performing a manipulation of the argument USER/PASSWORD results in hard-coded credentials. This vulnerability is known as CVE-2026-6610. Remote exploitation of the attack is possible. Furthermore, an exploit is available. The vendor was contacted early about this disclosure but did not respond in any way.

Detailsinfo

A vulnerability classified as problematic has been found in liangliangyy DjangoBlog up to 2.1.0.0. This affects some unknown processing of the file djangoblog/settings.py of the component Setting Handler. The manipulation of the argument USER/PASSWORD with an unknown input leads to a hard-coded credentials vulnerability. CWE is classifying the issue as CWE-798. The product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. This is going to have an impact on confidentiality.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-6610. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1110.001 for this issue.

The exploit is shared for download at github.com. It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way.

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 the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Content Management System

Vendor

• liangliangyy

Name

• DjangoBlog

Version

• 2.1.0

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Submitinfo

Accepted

• Submit #790289: liangliangyy DjangoBlog <= 2.1.0.0 Security Misconfiguration + Hardcoded Credentials (by Dem0)

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion