Skip to main content
CVE-2025-8162VulnerabilityPublished

CVE-2025-8162: deerwms deer-wms-2 · SQL Injection

Affects deerwms deer-wms-2Source CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jul 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
GitHubdeerwms/deer-wms-2pkg:github/deerwms/deer-wms-2Other threatsAffected
  • =3.0
  • =3.1
  • =3.2
  • =3.3
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, European organizations should immediately audit their use of deer-wms-2 and identify any deployments running affected versions (3.0 to 3.3). Until official patches are released, organizations should implement the following specific measures: 1) Apply strict input validation and sanitization on the params[dataScope] parameter at the application or web server level to block malicious SQL payloads. 2) Employ Web Application Firewalls (WAFs) with custom rules targeting SQL injection patterns specific to the vulnerable endpoint. 3) Restrict network access to the deer-wms-2 system, limiting exposure to trusted internal networks and VPNs only. 4) Monitor logs for unusual query patterns or repeated access attempts to /system/dept/list that may indicate exploitation attempts. 5) Engage with the vendor for timely updates and patches and plan for rapid deployment once available. 6) Conduct security testing, including penetration testing focused on SQL injection vectors, to verify the effectiveness of mitigations. These targeted actions go beyond generic advice by focusing on the specific vulnerable parameter and endpoint, reducing attack surface and detection capabilities.

Description

A vulnerability, which was classified as critical, has been found in deerwms deer-wms-2 up to 3.3. Affected by this issue is some unknown functionality of the file /system/dept/list. The manipulation of the argument params[dataScope] leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…