# CVE-2025-7385: SQL Injection in GOV CMS

> Unauthenticated remote attackers can exploit blind SQL injection in the search query parameter to read sensitive data from GOV CMS databases.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2025
- **Updated:** 4 Sep 2025
- **Also known as:** GHSA-92m7-gm53-fg8x

## What is CVE-2025-7385?

CVE-2025-7385 is a critical SQL injection vulnerability in Concept Intermedia GOV CMS, published on 4 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Input from search query parameter in GOV CMS is not sanitized properly, leading to a Blind SQL injection vulnerability, which might be exploited by an unauthenticated remote attacker. 

Versions 4.0 and above are not affected.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2025-7385?


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

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

## Is CVE-2025-7385 being exploited?

There is no known exploitation of CVE-2025-7385 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7385 is a critical SQL injection vulnerability in Concept Intermedia GOV CMS, published on 4 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-7385 in the wild and no public exploit code.

Affected product: Concept Intermedia GOV CMS. 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-7385/ (Markdown: https://insights.sbomify.com/CVE-2025-7385/index.md)
```

## Sources

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

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