# CVE-2025-7167: code-projects Responsive Blog Site category.php sql injection

> Remote attackers can exploit SQL injection in category.php to read or modify database contents in Responsive Blog Site.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2025
- **Updated:** 8 Jul 2025
- **Also known as:** GHSA-hhgr-rqhx-wx8c

## What is CVE-2025-7167?

CVE-2025-7167 is a medium-severity SQL injection vulnerability in code-projects Responsive Blog Site, published on 8 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in code-projects Responsive Blog Site 1.0. It has been declared as critical. This vulnerability affects unknown code of the file /category.php. The manipulation of the argument ID leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

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-2025-7167?

It affects 1 product.


Products: Fabian Responsive Blog Site.

## How do I fix CVE-2025-7167?

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

## Is CVE-2025-7167 being exploited?

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

## Other vulnerabilities in code-projects Responsive Blog Site

- [CVE-2025-7166](https://insights.sbomify.com/CVE-2025-7166/): code-projects Responsive Blog Site single.php sql injection (medium 5.3)
- [CVE-2025-6353](https://insights.sbomify.com/CVE-2025-6353/): code-projects Responsive Blog search.php cross site scripting (medium 5.1)
- [CVE-2025-9929](https://insights.sbomify.com/CVE-2025-9929/): code-projects Responsive Blog Site blogs_view.php cross site scripting (medium 4.8)
- [CVE-2025-6347](https://insights.sbomify.com/CVE-2025-6347/): code-projects Responsive Blog pageViewMembers.php cross site scripting (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-7167 and fix it if it is affected.

What it is: CVE-2025-7167 is a medium-severity SQL injection vulnerability in code-projects Responsive Blog Site, published on 8 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-7167 exists.

Affected product: code-projects Responsive 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-2025-7167/ (Markdown: https://insights.sbomify.com/CVE-2025-7167/index.md)
```

## Sources

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

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