dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-29089

HIGH · 7.5 CVSS v3.1 Published 2025-09-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
An issue in TP-Link AX10 Ax1500 v.1.3.10 Build (20230130) allows a remote attacker to obtain sensitive information

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

Information disclosure vulnerability in TP-Link AX10 Ax1500 router firmware version 1.3.10 Build (20230130) allows remote unauthenticated attackers to obtain sensitive information. The specific attack vector and exact nature of exposed data is not detailed in available documentation.

MitigationMonitor TP-Link for firmware updates and apply patches when available; as an interim measure, restrict the router's management interface to trusted networks and disable remote management features if not required.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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. Identify the router model
    Log into the router web interface or check the device label to confirm it is a TP-Link AX10 Ax1500 model
    Affected if The device is not a TP-Link AX10 Ax1500
  2. Check installed firmware version
    Navigate to the router web interface (usually at 192.168.0.1), go to Status or System settings, and record the firmware version and build number displayed
    Affected if The firmware version is 1.3.10 Build (20230130)
  3. Verify remote management status
    In the router web interface, go to Advanced or System Tools, then to Remote Management settings, and check if remote management is enabled
    Affected if Remote management is turned on and allows access from external IP addresses
  4. Check management interface internet exposure
    Access your public IP address from an external network on the router's management port (typically 80 or 443) to confirm if the login page is reachable from the internet, or check port forwarding/firewall rules
    Affected if The router management interface is accessible from the public internet

You are affected if you own a TP-Link AX10 Ax1500 running firmware 1.3.10 Build (20230130) and have remote management enabled or the interface exposed to the internet

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

Monitor TP-Link for firmware updates and apply patches when available; as an interim measure, restrict the router's management interface to trusted networks and disable remote management features if not required.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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