CVE-2025-1641 is a high severity SQL injection flaw in Benner ModernaNet up to 1.1.0, scored 7.3. Attacker supplied input reaches a database query. Upgrade to 1.1.1. The record says exploit details are public, and it is not on the CISA KEV list.
What's affected
The CVE record lists Benner ModernaNet up to 1.1.0. The weakness sits in /AGE0000700/GetHorariosDoDia, through the a query parameter on that endpoint input.
- Product: Benner ModernaNet
- Affected: up to 1.1.0
- Fixed: 1.1.1
- Severity: High, CVSS 7.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L)
- Known exploited (CISA KEV): no, the record's kev flag is false
The record says upgrading to version 1.1.1 addresses the issue.
The record also says the exploit has been disclosed to the public and may be used. That is a statement about public technical details, not a statement that attacks are underway. KEV status is false, and nothing in the record claims in the wild exploitation.
How to check if you're exposed
Most teams meet this kind of product as a downloaded web application running on PHP or Java. These checks apply.
- Locate every install of Benner ModernaNet. Include staging copies and old demos, which are the ones that tend to stay unpatched.
- Read the version from the product's own files or admin page and compare it with up to 1.1.0 from the record.
- Check whether /AGE0000700/GetHorariosDoDia is reachable from outside. Your web server or proxy access log, searched for that path, tells you who has requested it.
- If you have the source, find where the a query parameter on that endpoint value is used. A quick start is
grep -rn "a" .in the project root, then follow the value to the query. Look for string concatenation into SQL rather than parameter binding.
A dependency scan will not find this class of bug in custom or bundled application code. It needs a code scan or a web scan of the running site.
What to do now
- Upgrade Benner ModernaNet to version 1.1.1, the version the record says addresses the issue. Take a backup first.
- Confirm the version afterwards from the product itself.
- Restrict the affected path at the web server or reverse proxy until a fix is in place, or take the instance off the internet.
- Give the database account used by the application the least privilege it needs. It should not be able to read or change more than the app requires.
- Search web logs for unusual requests to the path and for database errors that appeared around the same time.
- Run a code or web scan on the application to find other places where input reaches SQL the same way.
Why it matters
The weakness is SQL injection, an injection flaw where a value controlled by the user, here a query parameter on that endpoint, becomes part of a database query without being bound as data. The database then runs more than the developer meant.
The usual outcome is unauthorised reading or changing of stored records, and sometimes more depending on database rights. The vector says the attack needs no account or privileges (PR:N in the vector). Small PHP and Java web apps are often copied into production from tutorials or demo kits, then forgotten. They rarely get a patch pipeline, which is why this class keeps turning up.
The record maps this to CWE-74 (Injection), CWE-89 (SQL Injection).
Quick check
Is CVE-2025-1641 exploited in the wild?
The record's CISA KEV flag is false, and nothing in the record says attacks are underway. It does say the exploit has been disclosed to the public.
Is there a fix for Benner ModernaNet?
The record says upgrading to version 1.1.1 addresses the issue. Take a backup, upgrade, and confirm the version.
Sources
- Safeguard Gold entry for CVE-2025-1641
- CVE record data as supplied for this review (NVD description, CVSS vector, CWE list). The references below are listed in the record and were not all fetched for this page, so confirm details against the vendor before acting.
- https://github.com/yago3008/cves
- https://vuldb.com/?ctiid.296691
- https://vuldb.com/?id.296691
- https://vuldb.com/?submit.499875
Last reviewed: 19 October 2026.
