dbcve.org
OpenwrtOperating system

CVE-2025-20674

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-02
Fix available
A fix is available. Upgrade to after 7.6.7.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In wlan AP driver, there is a possible way to inject arbitrary packet due to a missing permission check. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: WCNCR00413202; Issue ID: MSV-3303.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A missing permission check in the WLAN AP driver allows remote attackers to inject arbitrary packets, leading to escalation of privilege. The vulnerability exists in the wireless driver component and can be exploited without user interaction, achieving critical severity due to the potential for full system compromise.

MitigationApply the vendor patch (WCNCR00413202) to the WLAN AP driver firmware. If patching is not immediately possible, consider network segmentation to limit exposure of affected wireless infrastructure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenwrtOperating system
Affected:= 19.07.0= 21.02.0= 23.05
Software Development KitApplication
Affected:<= 7.6.7.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the system firmware or SDK version
    For OpenWrt, run 'cat /etc/openwrt_release' or 'cat /etc/os-release'. For Mediatek SDK-based devices, check the firmware version via 'cat /etc/version' or the vendor's admin interface.
    Affected if The version matches 19.07.0, 21.02.0, or 23.05 for OpenWrt, or is 7.6.7.2 or lower for Mediatek SDK.
  2. Confirm WLAN AP functionality is enabled
    Check if wireless access point features are active by running 'iwconfig' or 'wlanconfig' commands, or checking running processes like hostapd or wpad via 'ps | grep -i wlan' or 'ps | grep hostapd'.
    Affected if A WLAN AP interface is listed or hostapd/wpad processes are running, indicating the vulnerable wireless driver component is loaded.
  3. Identify the wireless driver in use
    Run 'lsmod | grep -i wl' or 'cat /proc/net/wireless' to list loaded wireless kernel modules. For OpenWrt, check 'uci show wireless' to see the wireless configuration and driver type.
    Affected if The system uses a Mediatek wireless driver or a vendor-specific WLAN AP driver matching the affected component.
  4. Verify wireless interface configuration
    Run 'iw list' or 'wpa_cli status' to enumerate wireless interfaces and their current state. Check 'uci show network' for wireless network bridge configurations.
    Affected if An AP-mode wireless interface (typically named wlan0, wlan0-1, or similar) is present and configured.
  5. Check for any vendor-specific driver files
    Look for wireless driver files in /lib/modules/ or /etc/wireless/ using 'find /lib/modules -name '*wlan*' -o -name '*mt7*' 2>/dev/null'. For Mediatek SDK, check for files containing 'WCNCR00413202' or similar driver identifiers.
    Affected if Mediatek wireless driver files exist on the system, indicating the affected component is present.

The environment is affected if the device runs OpenWrt versions 19.07.0, 21.02.0, or 23.05, or Mediatek SDK version 7.6.7.2 or lower, AND has an active WLAN AP interface utilizing the vulnerable wireless driver component.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 7.6.7.2
Interim mitigation

Apply the vendor patch (WCNCR00413202) to the WLAN AP driver firmware. If patching is not immediately possible, consider network segmentation to limit exposure of affected wireless infrastructure.

Fix this in Openwrt Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-20674 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-20674 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data