Ac6 FirmwareOperating system · Tenda

CVE-2025-7914

HIGH · 8.8 CVSS v3.1 Published 2025-07-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
A vulnerability has been found in Tenda AC6 15.03.06.50 and classified as critical. Affected by this vulnerability is the function setparentcontrolinfo of the component httpd. The manipulation leads to buffer overflow. The attack can be launched remotely.

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 buffer overflow vulnerability exists in the Tenda AC6 router firmware (v15.03.06.50) within the httpd web server's setparentcontrolinfo function, which handles parental control settings. The vulnerability is remotely exploitable and allows manipulation of the function leading to buffer overflow, potentially enabling arbitrary code execution.

MitigationUpdate router firmware to a patched version once available; if no update exists, restrict network access to the router's web interface and consider replacing the device.

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
Ac6 FirmwareOperating system
Affected:= 15.03.06.50

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

CVSS:3.1/AV:N/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. Confirm Tenda AC6 router model
    Log into router admin interface or check device label to confirm model is Tenda AC6
    Affected if Device is not a Tenda AC6 router
  2. Identify firmware version
    In router admin panel, look for System/Firmware version information, typically under Administration or System Settings. Alternatively, check via telnet/SSH if enabled or examine firmware binary file if available.
    Affected if Firmware version is 15.03.06.50 exactly
  3. Verify httpd web server is running
    Check router processes via telnet/SSH login using 'ps' command to confirm httpd process is active, or access router web interface on port 80/443 to confirm web server responds
    Affected if httpd process is running and web interface is accessible
  4. Confirm parental control feature exists
    Navigate router admin interface to find Parental Control or Access Control settings menu to verify the feature is present in the firmware
    Affected if Parental Control feature exists in the web interface
  5. Check network exposure of admin interface
    Determine if router admin web interface (port 80/443) is accessible from WAN/internet by testing external access or checking port forwarding/firewall rules
    Affected if Web interface is exposed to untrusted networks (internet-accessible)

User is affected if running Tenda AC6 firmware version 15.03.06.50 with httpd running and parental control feature exposed to untrusted networks.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update router firmware to a patched version once available; if no update exists, restrict network access to the router's web interface and consider replacing the device.

Fix this in Ac6 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA6.0 h
32.0 hours of engineering $5,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-7914 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