CVE-2025-9377
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 · uneditedThe authenticated remote command execution (RCE) vulnerability exists in the Parental Control page on TP-Link Archer C7(EU) V2 and TL-WR841N/ND(MS) V9. This issue affects Archer C7(EU) V2: before 241108 and TL-WR841N/ND(MS) V9: before 241108. Both products have reached the status of EOL (end-of-life). It's recommending to purchase the new product to ensure better performance and security. If replacement is not an option in the short term, please use the second reference link to download and install the patch(es).
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 confidenceAuthenticated remote command execution vulnerability in the Parental Control page of TP-Link Archer C7(EU) V2 and TL-WR841N/ND(MS) V9 routers allows an attacker with valid credentials to execute arbitrary commands on the underlying operating system via insufficient input validation.
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< 241108< 241108< 241108CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the router admin interface (typically at 192.168.0.1 or 192.168.1.1) and check the Status or System page to confirm the exact model number. Look for 'Archer C7' (specifically V2) or 'TL-WR841N' or 'TL-WR841ND' (specifically V9).Affected if The device is not one of these three models (Archer C7 V2, TL-WR841N V9, or TL-WR841ND V9).
-
Check the firmware versionIn the router admin interface, navigate to Status or System Information and locate the firmware version field. Compare it against 241108.Affected if The firmware version is less than 241108 (for example, 240912, 230912, etc.).
-
Confirm Parental Control feature presenceLog into the router admin interface and check if there is a 'Parental Control' or 'Parental Controls' menu option available under the Advanced or Security settings.Affected if The Parental Control feature is present and accessible in the admin interface.
-
Assess administrative access exposureDetermine if the router admin interface is accessible from the WAN (internet) side. Check under Advanced settings for 'Remote Management' or 'Access from WAN' - verify whether it is enabled and on which ports.Affected if Remote management from WAN is enabled, increasing the attack surface for unauthenticated network attackers.
The device is affected if it is an Archer C7 V2, TL-WR841N V9, or TL-WR841ND V9 running firmware version below 241108 and the router admin interface is accessible to an attacker.
Generated from the published advisory. Verify against your own configuration.
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 · scoped241108
Upgrade firmware to version 241108 or later if available. Since both products are EOL and may not receive patches, consider network segmentation, disabling parental control features if unused, or replacing with a supported device.
Firmware version 241108 or later for TP-Link Archer C7 V2 and TL-WR841N/ND V9
- 1. Identify the exact model number of your TP-Link device (Archer C7 V2 or TL-WR841N/ND V9)
- 2. Visit TP-Link's official support page at www.tp-link.com and locate the firmware download section for your specific model
- 3. Download firmware version 241108 or later for your device model
- 4. Access your router's web management interface by entering the device's IP address in a web browser
- 5. Log in with administrator credentials
- 6. Navigate to System Tools > Firmware Upgrade (or similar menu option)
- 7. Click on Browse/Choose File and select the downloaded firmware file
- 8. Click Upgrade/Update to install the new firmware
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9377 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-9377 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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