# CVE-2025-6169: HAMASTAR Technology WIMP website co-construction management platform - SQL Injection

> Unauthenticated remote attackers can inject SQL commands to read, modify, and delete database contents in the WIMP website co-construction management platform.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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:** 16 Jun 2025
- **Updated:** 16 Jun 2025
- **Also known as:** GHSA-gpg7-49w7-q7wr

## What is CVE-2025-6169?

CVE-2025-6169 is a critical SQL injection vulnerability in HAMASTAR Technology WIMP, published on 16 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WIMP website co-construction management platform from HAMASTAR Technology has a SQL Injection vulnerability, allowing unauthenticated remote attackers to inject arbitrary SQL commands to read, modify, and delete database contents.

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

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


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

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

## Is CVE-2025-6169 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6169 is a critical SQL injection vulnerability in HAMASTAR Technology WIMP, published on 16 Jun 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-6169 in the wild and no public exploit code.

Affected product: HAMASTAR Technology WIMP. 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-6169/ (Markdown: https://insights.sbomify.com/CVE-2025-6169/index.md)
```

## Sources

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

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