# CVE-2018-25156: Teradek Cube 7.3.6 Cross-Site Request Forgery Password Change

> Attackers can force administrative password changes on Teradek Cube devices via CSRF, leading to account takeover.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **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:** 24 Dec 2025
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-m2m8-9ppp-q3c7

## What is CVE-2018-25156?

CVE-2018-25156 is a medium-severity vulnerability in Teradek, LLC Cube, published on 24 Dec 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

Teradek Cube 7.3.6 contains a cross-site request forgery vulnerability that allows attackers to change administrative passwords without proper request validation. Attackers can craft a malicious web page with a hidden form to submit password change requests to the device's system configuration interface.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2018-25156?

It affects 1 product.


Products: Teradek Cube Firmware.

## How do I fix CVE-2018-25156?

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

## Is CVE-2018-25156 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25156 and fix it if it is affected.

What it is: CVE-2018-25156 is a medium-severity vulnerability in Teradek, LLC Cube, published on 24 Dec 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-2018-25156 exists.

Affected product: Teradek, LLC Cube. 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-2018-25156/ (Markdown: https://insights.sbomify.com/CVE-2018-25156/index.md)
```

## Sources

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

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