dbcve.org
Software Development KitApplication · Mediatek

CVE-2025-20713

HIGH · 7.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 →
80/100
Remediation priority · High
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 local escalation of privilege if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation. Patch ID: WCNCR00432661; Issue ID: MSV-3904.

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 local privilege escalation vulnerability exists in the WLAN AP driver where an incorrect bounds check leads to an out-of-bounds write. An attacker who already has System-level privileges can exploit this to escalate to higher privileges. No user interaction is required for exploitation.

MitigationApply vendor patch WCNCR00432661 immediately to affected systems. Since exploitation requires System-level access, prioritize patch deployment on systems where privileged actors or malware could potentially gain System access.

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Check OpenWrt version
    Run 'cat /etc/os-release' or 'cat /etc/openwrt_version' to identify the installed OpenWrt release version
    Affected if Version shows 19.07.0 or 21.02.0
  2. Check Mediatek SDK version
    Check firmware/system information via 'cat /proc/version' or review SDK documentation to identify the Mediatek Software Development Kit version number
    Affected if SDK version is 7.6.7.2 or earlier
  3. Identify WLAN AP driver presence
    Check for loaded wireless AP driver modules via 'lsmod' or review network interface configuration for Mediatek wireless AP interfaces
    Affected if WLAN AP driver (Mediatek wireless driver) is loaded and active on the system
  4. Verify System-level access requirement
    Confirm current user context - exploitation requires existing System or Administrator privileges as a prerequisite
    Affected if System-level access is already present and the affected WLAN AP driver is in use on vulnerable version

You are affected if running Mediatek SDK <= 7.6.7.2 or OpenWrt 19.07.0/21.02.0 with the Mediatek WLAN AP driver loaded and active, and an attacker already has System-level access on the device.

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 vendor patch WCNCR00432661 immediately to affected systems. Since exploitation requires System-level access, prioritize patch deployment on systems where privileged actors or malware could potentially gain System access.

Recommended fix Moderate confidence

MediaTek SDK > 7.6.7.2 (contact MediaTek for exact fixed release); OpenWrt newer versions with updated MediaTek driver packages

  1. Identify the MediaTek WiFi driver component in your deployment that includes the wlan AP driver (typically found in SDK-based firmware or OpenWrt images using MediaTek chipsets)
  2. Consult MediaTek's official security advisory at corp.mediatek.com for the specific fixed SDK release containing patch WCNCR00432661
  3. Upgrade the MediaTek Software Development Kit to a version newer than 7.6.7.2 that includes the patch (contact MediaTek directly for the exact fixed release number)
  4. For OpenWrt deployments: Rebuild or obtain an updated OpenWrt image for versions 19.07.0 or 21.02.0 that incorporates the MediaTek driver fix, or migrate to a newer OpenWrt branch if available
  5. Verify the upgrade by reviewing the wlan driver version and confirming the bounds check fix is applied
Caveat SDK upgrades may require regression testing of WiFi functionality; driver changes could affect AP configuration parameters

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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