dbcve.org
Adp Application Developer PlatformApplication · Zhilink

CVE-2025-8806

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
A vulnerability was found in zhilink 智互联(深圳)科技有限公司 ADP Application Developer Platform 应用开发者平台 1.0.0. It has been classified as critical. This affects an unknown part of the file /adpweb/a/sys/office/treeData. The manipulation of the argument extId leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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 confidence

A SQL injection vulnerability exists in zhiling ADP Application Developer Platform version 1.0.0. The vulnerability is located in the /adpweb/a/sys/office/treeData endpoint where the extId parameter is not properly sanitized before being used in SQL queries. This allows remote attackers to inject malicious SQL statements. The exploit is publicly available and the vendor has not responded to disclosure attempts.

MitigationSince the vendor is unresponsive, implement parameterized queries/prepared statements for the extId parameter in the treeData endpoint, or deploy a WAF rule to filter SQL injection payloads as a compensating control until proper code-level remediation can be performed.

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
Adp Application Developer PlatformApplication
Affected:= 1.0.0

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 Zhilink ADP is installed
    Locate the ADP Application Developer Platform installation by checking for the /adpweb directory structure on the web server, or identify the running service responding on ports typically used by the application.
    Affected if The product is present and running on the system.
  2. Verify the installed version is 1.0.0
    Check the application's version information through the admin interface, version file in the installation directory, or by making a request to the application and inspecting response headers or error messages that may reveal version details.
    Affected if The installed version matches 1.0.0 exactly.
  3. Determine if the treeData endpoint is exposed
    Attempt to access the URL path /adpweb/a/sys/office/treeData via HTTP request and observe whether the endpoint responds (even with an error).
    Affected if The endpoint is accessible and returns any response.
  4. Inspect the extId parameter handling
    Send a request to /adpweb/a/sys/office/treeData with a test value in the extId parameter (e.g., extId=test) and observe the application's response for SQL syntax errors, database errors, or unexpected behavior indicating unsanitized parameter use.
    Affected if The application returns database-related errors or executes the supplied value in a SQL context.
  5. Verify SQL injection is possible
    Compare responses from benign input versus known SQL injection patterns in the extId parameter (such as extId=1' OR '1'='1) to detect differences indicating SQL query manipulation.
    Affected if Responses differ between normal input and SQL injection patterns in a way that suggests the parameter is not properly sanitized.

The environment is affected if Zhilink ADP Application Developer Platform version 1.0.0 is installed and the /adpweb/a/sys/office/treeData endpoint with the extId parameter is accessible without proper input sanitization.

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

Since the vendor is unresponsive, implement parameterized queries/prepared statements for the extId parameter in the treeData endpoint, or deploy a WAF rule to filter SQL injection payloads as a compensating control until proper code-level remediation can be performed.

Fix this in Adp Application Developer Platform Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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