CVE Intelligence
Analysis AI-assisted

CVE-2019-25298: html5_snmp 1.11 SQL Injection via Router_ID and Router_IP Parameters

CVE-2019-25298 describes multiple SQL injection flaws in html5_snmp 1.11, a product attributed to Lolypop55, affecting the Router_ID and Router_IP parameters. NVD and VulnCheck rate it critical with a CVSS 3.1 base score of 9.1, and the record is classified as CWE-89. CISA KEV does not list it and no confirmed exploitation appears in the sources consulted, though an Exploit-DB entry is referenced.

Published Oct 13, 2026 · Updated Oct 13, 2026 · Ler em português

Overview

The CVE record describes multiple SQL injection vulnerabilities in html5_snmp 1.11, a product attributed to Lolypop55. The flaws are reachable through the Router_ID and Router_IP parameters and are classified as CWE-89 (SQL Injection). The record was published on 2026-02-06 and has the source status Modified.

Impact

  • According to the description, an attacker could manipulate database queries and potentially extract or modify database information.
  • NVD and VulnCheck score the issue at 9.1 under CVSS 3.1, rated critical. The vector indicates network reachability, low complexity, no privileges required and no user interaction, with high integrity and availability impact and no confidentiality impact.
  • VulnCheck also provides a CVSS 4.0 score of 7.1.

Affected products and versions

  • Product: Lolypop55 Html5 Snmp, with the version 1.11 named in the description.
  • The affected version range is not specified by the source.
  • No fixed version is listed in the record. This does not confirm that a fix is unavailable.
  • The product repository on GitHub is referenced by the record.

Exploitation status

  • The CISA KEV catalog does not list this CVE, so no active exploitation is claimed here.
  • No EPSS score is present in the record.
  • An Exploit-DB entry is referenced with the tag Exploit. Its presence means public exploit material may exist, which increases the need for prompt defensive action. Its contents are not reproduced here.
  • No confirmed exploitation appears in the sources consulted.

Remediation and mitigation

  • Identify whether html5_snmp is deployed in your environment, including any internal or test instances.
  • Since no fixed version is documented, consider isolating or removing the component until the maintainer provides a verified update or until the code is reviewed.
  • Restrict network access to the affected application, especially for untrusted users.
  • Use database accounts with the minimum privileges required and separate application credentials from administrative ones.
  • Review the application code so that user-supplied values are handled through parameterized queries and strict input validation.
  • A web application firewall may reduce exposure as a temporary compensating control, but it is not a substitute for a code fix.

Detection guidance

  • Review web server and application logs for unusual or malformed values in the Router_ID and Router_IP parameters.
  • Look for database error messages returned to clients, unexpected delays in responses, or unusual query result volumes.
  • Monitor database logs for queries that do not match expected application behavior.
  • Alert on changes to database content tied to the affected application.

Limitations of the available information

  • The affected version range is not specified, so it is unknown which builds are vulnerable beyond the 1.11 version named in the description.
  • No fixed version or vendor advisory is listed. The VulnCheck advisory link is tagged as broken in the record.
  • No EPSS or SSVC data is present.
  • The analysis relies on the record and the listed references and has not been independently tested.

Frequently asked questions

Is CVE-2019-25298 known to be actively exploited?

CISA KEV does not list this CVE, and no confirmed exploitation appears in the sources consulted. The record does reference an Exploit-DB entry, so defenders should treat public exploit material as possible.

Which versions are affected?

The source does not specify the affected version range. The description names html5_snmp 1.11, but no fixed version is listed in the record.

What should administrators do now?

Identify deployments, restrict network access, use least-privilege database accounts, and consider isolating the component until a verified fix or code review is complete.

This analysis was drafted with AI assistance from verified source data and automatically checked against it.