# CVE-2019-25298: html5_snmp 1.11 - 'Router_ID' SQL Injection

> Attackers can exploit SQL injection in html5_snmp to extract or modify database information via crafted Router_ID and Router_IP parameters.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Feb 2026
- **Updated:** 2 Mar 2026
- **Also known as:** GHSA-5g55-vg6f-jp94

## What is CVE-2019-25298?

CVE-2019-25298 is a high-severity SQL injection vulnerability in lolypop55 html5_snmp, published on 6 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

html5_snmp 1.11 contains multiple SQL injection vulnerabilities that allow attackers to manipulate database queries through Router_ID and Router_IP parameters. Attackers can exploit error-based, time-based, and union-based injection techniques to potentially extract or modify database information by sending crafted payloads.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2019-25298?

It affects 1 product.


Products: Lolypop55 Html5 Snmp.

## How do I fix CVE-2019-25298?

No fix has been published for CVE-2019-25298 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-25298 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25298 exists.

## Other vulnerabilities in lolypop55 html5_snmp

- [CVE-2019-25294](https://insights.sbomify.com/CVE-2019-25294/): html5_snmp 1.11 - 'Remark' Persistent Cross-Site Scripting (medium 5.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25298 and fix it if it is affected.

What it is: CVE-2019-25298 is a high-severity SQL injection vulnerability in lolypop55 html5_snmp, published on 6 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25298 exists.

Affected product: lolypop55 html5_snmp. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-25298/ (Markdown: https://insights.sbomify.com/CVE-2019-25298/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-25298
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-25298
- OSV: https://osv.dev/vulnerability/CVE-2019-25298

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-25298/
Summaries are generated and may contain mistakes; the official description above is the record.