# CVE-2024-25343: Security feature bypass in n/a

> Attackers can bypass security policies to create weak passwords on Tenda N300 F3 routers, compromising device security.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Apr 2024
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-3wqg-6hfx-9w42

## What is CVE-2024-25343?

CVE-2024-25343 is a critical vulnerability in n/a, published on 26 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Tenda N300 F3 router vulnerability allows users to bypass intended security policy and create weak passwords.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2024-25343?

It affects 1 product.


Products: Tenda N300 Firmware.

## How do I fix CVE-2024-25343?

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

## Is CVE-2024-25343 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-4498](https://insights.sbomify.com/CVE-2023-4498/): Authentication Bypass in Tenda N300 Wireless N VDSL2 Modem Router (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-25343 and fix it if it is affected.

What it is: CVE-2024-25343 is a critical vulnerability in n/a, published on 26 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-25343 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-2024-25343/ (Markdown: https://insights.sbomify.com/CVE-2024-25343/index.md)
```

## Sources

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

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