CVE-2025-8125 is a medium (CVSS 6.3) SQL injection in deerwms deer-wms-2 (deer-wms-2 up to 3.3). The record names no fixed version, so plan on isolating or replacing it. Do not expose the product to untrusted networks until you have confirmed a fix.
What's affected
The record lists deer-wms-2 up to 3.3 as affected. The vulnerable code is in /system/role/authUser/allocatedList, through the params[dataScope] argument.
No fixed version is named in the record or the issue.
The issue says the value is placed into the mapper query by raw string substitution, written as a dollar sign placeholder, rather than as a bound parameter. In MyBatis style mappers that is the classic pattern: the hash placeholder binds, the dollar placeholder pastes text into the SQL.
The record's CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L, a score of 6.3. The Gitee issue shows no comments and a to do status. It was filed by an account named ZAST and labeled a code security bug.
The record also says the exploit has been disclosed to the public and may be used. That is not the same as confirmed attacks: this CVE is not in CISA's Known Exploited Vulnerabilities catalog (the record's kev flag is false).
How to check if you're exposed
Find out whether the component is deployed in your estate. These products often arrive inside a larger system, so check your server inventory and your web application directories:
find / -name "allocatedList" -not -path "/proc/*" 2>/dev/null | head
Then check your web server or reverse proxy logs for requests to that path from addresses you do not recognize.
A free in-browser dependency scan at gold.safeguard.sh/scan can show whether this CVE appears in a project's dependency list. Note that it covers packages. Stand-alone applications and firmware are best checked against your own inventory.
What to do now
- Confirm whether you run deer-wms-2 and in which version.
- Take it off any internet facing host, or put it behind authentication at the web server or VPN, until a fix exists.
- Check the vendor or project site for a newer release. No fix is named in the record.
- Put a WAF rule in front of the allocatedList endpoint as a stopgap. A WAF reduces risk but does not fix the code.
- If you maintain the code, replace string built queries with parameterized queries, and use a database account with the least privilege the application needs.
If you maintain a codebase and want to know whether a vulnerable package is actually called, Safeguard's reachability analysis separates packages that are present from code paths that are used.
Why it matters
The weakness class here is CWE-74 (injection), CWE-89 (SQL injection). SQL injection happens when user input is joined into a query string, so the database cannot tell the developer's command from the visitor's data. The standard fix is a parameterized query, which keeps the two apart. When the vulnerable field sits on a login or admin page, the code runs before any check on who is asking.
The record notes that the exploit has been disclosed to the public. Small PHP and Java projects like this are often installed without a security review and never updated, which makes published findings useful to anyone scanning for them.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Is there a patch for CVE-2025-8125?
The record does not name a fixed version, and for PAD CMS CERT Polska says none will be published. Treat the product as unpatched, reduce its exposure and check the vendor or project site for news.
Is CVE-2025-8125 being exploited in the wild?
The record's kev flag is false, so it is not in CISA's Known Exploited Vulnerabilities catalog. The record does say the exploit has been disclosed to the public, so assume attackers can find it.
Sources
- Safeguard Gold entry for CVE-2025-8125
- Gitee issue ICLRE9
- NVD record data for CVE-2025-8125, published 2025-07-25, source cna@vuldb.com
Last reviewed: 18 October 2026.
