# CVE-2026-6610: liangliangyy DjangoBlog Setting settings.py hard-coded credentials

> Hard-coded credentials in DjangoBlog settings allow remote attackers to potentially access sensitive data or take over accounts.

- **Severity:** Medium 6.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Apr 2026
- **Updated:** 20 Apr 2026
- **Also known as:** GHSA-gccw-6jq7-5553

## What is CVE-2026-6610?

CVE-2026-6610 is a medium-severity vulnerability in liangliangyy DjangoBlog, published on 20 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-259 (Use of Hard-coded Password)

## Which versions are affected by CVE-2026-6610?


## How do I fix CVE-2026-6610?

No fix has been published for CVE-2026-6610 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-6610 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6610 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6610 and fix it if it is affected.

What it is: CVE-2026-6610 is a medium-severity vulnerability in liangliangyy DjangoBlog, published on 20 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6610 exists.

Affected product: liangliangyy DjangoBlog. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6610/ (Markdown: https://insights.sbomify.com/CVE-2026-6610/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6610
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6610
- OSV: https://osv.dev/vulnerability/CVE-2026-6610

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6610/
Summaries are generated and may contain mistakes; the official description above is the record.