# CVE-2026-5805: code-projects Easy Blog Site contact_us.php sql injection

> Remote attackers can exploit SQL injection in the contact form to read or modify database contents in Easy Blog Site.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/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:** 8 Apr 2026
- **Updated:** 9 Apr 2026
- **Also known as:** GHSA-48h8-qxm4-xrp8

## What is CVE-2026-5805?

CVE-2026-5805 is a medium-severity SQL injection vulnerability in code-projects Easy Blog Site, published on 8 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A weakness has been identified in code-projects Easy Blog Site up to 1.0. The impacted element is an unknown function of the file /users/contact_us.php. Executing a manipulation of the argument Name can lead to sql injection. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

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

## Is CVE-2026-5805 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5805 is a medium-severity SQL injection vulnerability in code-projects Easy Blog Site, published on 8 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-5805 exists.

Affected product: code-projects Easy Blog Site. 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-5805/ (Markdown: https://insights.sbomify.com/CVE-2026-5805/index.md)
```

## Sources

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

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