# CVE-2025-5439: Linksys RE6500/RE6250/RE6300/RE6350/RE7000/RE9000 verifyFacebookLike os command injection

> Remote attackers can execute arbitrary OS commands on Linksys range extenders via the verifyFacebookLike endpoint due to improper input validation.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/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:** 2 Jun 2025
- **Updated:** 2 Jun 2025
- **Also known as:** GHSA-whjq-92qp-qg76

## What is CVE-2025-5439?

CVE-2025-5439 is a medium-severity command injection vulnerability in Linksys Re6250 Firmware, published on 2 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in Linksys RE6500, RE6250, RE6300, RE6350, RE7000 and RE9000 1.0.013.001/1.0.04.001/1.0.04.002/1.1.05.003/1.2.07.001. It has been rated as critical. Affected by this issue is the function verifyFacebookLike of the file /goform/verifyFacebookLike. The manipulation of the argument uid/accessToken leads to os command injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 6 products.


Products: Linksys Re6250 Firmware, Linksys Re6300 Firmware, Linksys Re6350 Firmware, Linksys Re6500 Firmware, Linksys Re7000 Firmware, Linksys Re9000 Firmware.

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

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

## Is CVE-2025-5439 being exploited?

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

## Other vulnerabilities in Linksys Re6250 Firmware

- [CVE-2025-14133](https://insights.sbomify.com/CVE-2025-14133/): Memory corruption in RE6250 (high 8.7)
- [CVE-2025-14134](https://insights.sbomify.com/CVE-2025-14134/): Linksys RE6500/RE6250/RE6300/RE6350/RE7000/RE9000 mod_form.so stack-based overflow (high 8.7)
- [CVE-2025-14135](https://insights.sbomify.com/CVE-2025-14135/): Memory corruption in RE6250 (high 8.7)
- [CVE-2025-14136](https://insights.sbomify.com/CVE-2025-14136/): Linksys RE6500/RE6250/RE6300/RE6350/RE7000/RE9000 mod_form.so stack-based overflow (high 8.7)
- [CVE-2025-9481](https://insights.sbomify.com/CVE-2025-9481/): Linksys RE6250/RE6300/RE6350/RE6500/RE7000/RE9000 setIpv6 stack-based overflow (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-5439 is a medium-severity command injection vulnerability in Linksys Re6250 Firmware, published on 2 Jun 2025. 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-2025-5439 exists.

Affected product: Linksys Re6250 Firmware. 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-5439/ (Markdown: https://insights.sbomify.com/CVE-2025-5439/index.md)
```

## Sources

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

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