Skip to main content
CVE-2025-8126VulnerabilityPublished

CVE-2025-8126: 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, 08:30 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 26 Oct 2026.

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

Given the absence of official patches or updates linked in the provided information, European organizations should implement immediate compensating controls. These include: 1) Restricting network access to the deer-wms-2 application, limiting it to trusted internal IP ranges and VPN connections to reduce exposure to remote attackers. 2) Implementing Web Application Firewall (WAF) rules specifically designed to detect and block SQL injection attempts targeting the params[dataScope] parameter. 3) Conducting thorough input validation and sanitization on the params[dataScope] parameter at the application or proxy level if possible. 4) Monitoring application logs and database query logs for unusual or suspicious activity indicative of SQL injection attempts. 5) Applying the principle of least privilege to database accounts used by deer-wms-2, ensuring they have only the minimum necessary permissions to limit the impact of a successful injection. 6) Planning and prioritizing an upgrade or patch deployment once an official fix is released by the vendor. 7) Conducting security awareness training for IT staff to recognize and respond to exploitation attempts promptly.

Description

A vulnerability classified as critical has been found in deerwms deer-wms-2 up to 3.3. This affects an unknown part of the file /system/user/export. 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…