# CVE-2025-28030: Memory corruption in n/a

> A stack overflow in the setParentalRules function allows attackers to execute arbitrary code or cause denial of service on TOTOLINK A810R routers.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Apr 2025
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-rgcr-wg7p-29p2

## What is CVE-2025-28030?

CVE-2025-28030 is a high-severity memory corruption vulnerability in n/a, published on 22 Apr 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

TOTOLINK A810R V4.1.2cu.5182_B20201026 was discovered to contain a stack overflow via the startTime and endTime parameters in setParentalRules function.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2025-28030?

It affects 1 product.


Products: Totolink A810r Firmware.

## How do I fix CVE-2025-28030?

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

## Is CVE-2025-28030 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-28024](https://insights.sbomify.com/CVE-2025-28024/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-28037](https://insights.sbomify.com/CVE-2025-28037/): Command injection in n/a (critical 9.8)
- [CVE-2025-28137](https://insights.sbomify.com/CVE-2025-28137/): Command injection in n/a (critical 9.8)
- [CVE-2022-25079](https://insights.sbomify.com/CVE-2022-25079/): Command injection in n/a (critical 9.8)
- [CVE-2024-53334](https://insights.sbomify.com/CVE-2024-53334/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-28030 and fix it if it is affected.

What it is: CVE-2025-28030 is a high-severity memory corruption vulnerability in n/a, published on 22 Apr 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-28030 exists.

Affected product: n/a. 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-2025-28030/ (Markdown: https://insights.sbomify.com/CVE-2025-28030/index.md)
```

## Sources

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

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