CVE-2025-9377
The 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).
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? Partly. OS command injection puts shell syntax into the request. WAF rules catch common shell commands but miss encoded or unusual payloads.
Also consider: shlex/execve-style APIs
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-9377 being exploited?
Yes. CVE-2025-9377 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-9377?
CVE-2025-9377 is rated High with a CVSS score of 7.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-9377?
Yes. A fix has been recorded for CVE-2025-9377. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-9377 affect?
CVE-2025-9377 affects tp-link:tl-wr841n_firmware, tp-link:tl-wr841nd_firmware, tp-link:archer_c7_firmware. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected< 241108
- affected< 241108
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 3 Sept 2025 (SSVC 2.0.3).
timeline
- 29 Aug 2025Published
- 3 Sept 2025Added to CISA KEV (exploited in the wild) · 4 days later
- 3 Sept 2025CISA SSVC assessment: exploitation active · same day later
- 24 Sept 2025CISA remediation due date (US federal agencies) · 21 days later
- 26 Feb 2026CVE record last updated · 156 days (about 5 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 249 days (about 8 months) later
- Advisorytp-link.com /us/support/faq/4365/
- Patchtp-link.com /us/support/faq/4308/
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-9377
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.