Skip to main content
CVE-2025-8163VulnerabilityPublished

CVE-2025-8163: 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, 07:57 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 40% 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

Organizations should immediately audit their use of deer-wms-2 and identify any instances running versions 3.0 to 3.3. Since no official patches are currently linked, mitigation should focus on restricting access to the affected endpoint (/system/role/list) by implementing strict network segmentation and access controls, limiting the exposure of the vulnerable interface to trusted users only. Input validation and web application firewalls (WAFs) should be configured to detect and block suspicious SQL injection patterns targeting the params[dataScope] parameter. Monitoring logs for unusual query patterns or access attempts to the vulnerable endpoint is critical. Additionally, organizations should enforce the principle of least privilege to reduce the risk posed by low-privilege accounts. Engaging with the vendor for timely patch releases or applying custom fixes to sanitize inputs may be necessary. Finally, preparing incident response plans to quickly address any exploitation attempts will help minimize impact.

Description

A vulnerability, which was classified as critical, was found in deerwms deer-wms-2 up to 3.3. This affects an unknown part of the file /system/role/list. The manipulation of the argument params[dataScope] leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…