dbcve.org
Software Development KitApplication · Mediatek

CVE-2025-20711

HIGH · 8.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to after 7.6.7.2 or later.
See remediation →
93/100
Remediation priority · Urgent
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 out of bounds write due to an incorrect bounds check. This could lead to remote (proximal/adjacent) escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: WCNCR00422399; Issue ID: MSV-3748.

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 · high confidence

A vulnerability in the WLAN AP driver allows an attacker within wireless proximity to trigger an out-of-bounds write operation. The root cause is an incorrect bounds check in the driver code, which can be exploited without authentication or user interaction to achieve privilege escalation.

MitigationApply the vendor-supplied firmware patch (WCNCR00422399) to the affected WLAN AP devices. Until patching is feasible, limit physical/wireless proximity to trusted networks only.

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
Software Development KitApplication
Affected:<= 7.6.7.2
OpenwrtOperating system
Affected:= 19.07.0= 21.02.0

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/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 Mediatek SDK version
    Check the installed Mediatek Software Development Kit version. This is typically found in system information, firmware metadata, or by querying the SDK packages if accessible. On embedded devices, this may be visible in /etc/version, /proc/version, or vendor-specific diagnostic interfaces.
    Affected if The SDK version is 7.6.7.2 or lower.
  2. Identify OpenWRT version
    Check the running OpenWRT version. This can be obtained via 'cat /etc/os-release' or by viewing the system information in the OpenWRT LuCI interface or via 'cat /etc/openwrt_version' if available.
    Affected if The OpenWRT version is exactly 19.07.0 or exactly 21.02.0.
  3. Confirm AP mode is active
    Verify that the wireless interface is configured and operating in Access Point (AP) mode. This can be checked by examining wireless configuration files, running 'iwconfig' or 'iw' commands to see interface mode, or checking hostapd configuration if used.
    Affected if AP mode is enabled and the wireless driver is handling AP-mode operations.
  4. Locate wireless driver component
    Identify the WLAN driver in use. On Mediatek-based devices, this is typically a vendor-specific wireless driver. Check loaded kernel modules via 'lsmod' or examine the wireless subsystem configuration.
    Affected if The Mediatek WLAN AP driver component is present and loaded.

A user is affected if they are running Mediatek SDK <= 7.6.7.2 or OpenWRT 19.07.0/21.02.0 with the wireless driver configured in AP mode.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 7.6.7.2
Interim mitigation

Apply the vendor-supplied firmware patch (WCNCR00422399) to the affected WLAN AP devices. Until patching is feasible, limit physical/wireless proximity to trusted networks only.

Recommended fix Moderate confidence

SDK: any version > 7.6.7.2 that includes patch WCNCR00422399; OpenWrt: upgrade to 22.03 or later stable release

  1. For MediaTek Software Development Kit (SDK): Upgrade to a version newer than 7.6.7.2 that includes patch WCNCR00422399
  2. For OpenWrt 19.07.0: Upgrade to a newer supported OpenWrt version (such as 22.03 or later) that contains the fixed driver
  3. For OpenWrt 21.02.0: Upgrade to a newer supported OpenWrt version (such as 22.03 or later) that contains the fixed driver
  4. After upgrade, verify the WLAN AP driver is updated by checking system logs or driver version information
  5. Confirm the vulnerability is resolved by reviewing MediaTek release notes for the new SDK version
Caveat OpenWrt major version upgrades may require configuration migration and package reinstallation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Software Development Kit Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-20711 — 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-20711 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