CVE-2025-15568
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 · uneditedA command injection vulnerability was identified in the web module of Archer AXE75 v1.6/v1.0 router. An authenticated attacker with adjacent-network access may be able to perform remote code execution (RCE) when the router is configured with sysmode=ap. Successful exploitation results in root-level privileges and impacts confidentiality, integrity and availability of the device. This issue affects Archer AXE75 v1.6/v1.0: through 1.3.2 Build 20250107.
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 confidenceCommand injection vulnerability in the web module of TP-Link Archer AXE75 router (v1.6/v1.0 through 1.3.2 Build 20250107). An authenticated attacker with adjacent network access can achieve root-level RCE by injecting arbitrary commands through the web interface, but only when the router is configured in AP mode (sysmode=ap).
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< 1.3.2= 1.3.2CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the router modelLog into the router web interface and check the device model under Status or System section, or physically inspect the device label for 'Archer AXE75'.Affected if The device is not a TP-Link Archer AXE75 - this vulnerability only affects that specific model.
-
Check the installed firmware versionIn the router web interface, navigate to System > Firmware Upgrade or Status page and locate the firmware version string (for example: 1.3.2 Build 20250107).Affected if Firmware version is less than 1.3.2, or equals exactly 1.3.2 Build 20250107.
-
Verify if AP mode is enabledIn the router web interface, go to Operation Mode or System settings and check whether the router is configured in AP mode. Alternatively, check the sysmode parameter value via CLI if accessible.Affected if The router is configured in AP mode (sysmode=ap). The vulnerability only triggers when this mode is active.
-
Check for unauthorized configuration changesReview the router configuration for unexpected port forwards, firewall rules, or admin account changes that may indicate prior exploitation.Affected if Unexpected modifications exist that were not made by the administrator.
You are affected if you own an Archer AXE75 router running firmware version 1.3.2 or below AND the router is configured to operate in AP mode.
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.
From vendor data1.3.2
Apply vendor-supplied firmware patch when available. Until then, avoid using AP mode if possible and restrict network access to trusted users only.
- Consultation3.0 h
- Testing6.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 $2,976.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-15568 — 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-15568 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