Skip to main content
VulnerabilityPublished

CVE-2025-6169: HAMASTAR Technology WIMP · SQL Injection

Affects HAMASTAR Technology WIMPSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
HAMASTAR Technology WIMPAffected
  • =0
Fixed in–

AI-suggested

  1. Immediate mitigation should focus on isolating the WIMP platform from direct internet exposure by placing it behind a secure VPN or firewall restricting access to trusted IPs only.
  2. Conduct a thorough code review and implement parameterized queries or prepared statements to eliminate SQL injection vectors in the application code.
  3. Employ web application firewalls (WAFs) with custom rules to detect and block SQL injection payloads targeting the WIMP platform until an official patch is released.
  4. Monitor database and application logs for unusual query patterns or error messages indicative of injection attempts.
  5. Restrict database user privileges to the minimum necessary, preventing unauthorized data modification or deletion even if injection occurs.
  6. Engage with HAMASTAR Technology for timely updates or patches and plan for rapid deployment once available.
  7. Educate internal security teams and developers about SQL injection risks and secure coding practices to prevent similar vulnerabilities.
  8. Consider alternative platforms or temporary suspension of WIMP usage if critical projects are at risk and no immediate patch is available.

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.

References

Community reviews

Loading reviews…