dbcve.org
Adp Application Developer PlatformApplication · Zhilink

CVE-2025-6267

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-19
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 rated as critical. This issue affects some unknown processing of the file /adpweb/a/base/barcodeDetail/. The manipulation of the argument barcodeNo/barcode/itemNo leads to sql injection. The attack may be initiated remotely. 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 zhilink ADP Application Developer Platform 1.0.0 in the /adpweb/a/base/barcodeDetail/ endpoint. The barcodeNo, barcode, or itemNo parameters are not properly sanitized before being used in database queries, allowing remote attackers to inject arbitrary SQL commands.

MitigationImplement parameterized queries or prepared statements for all database operations involving user-supplied input. Apply input validation and employ least-privilege database accounts to limit the impact of any successful injection.

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. Identify installed product and version
    Locate the zhilink ADP Application Developer Platform installation and determine its version number. Check application metadata, about pages, or installation directories for version 1.0.0.
    Affected if The installed version is exactly 1.0.0 of Zhilink ADP Application Developer Platform
  2. Verify barcodeDetail endpoint is accessible
    Confirm the web application is running and the /adpweb/a/base/barcodeDetail/ endpoint is reachable. Use a browser or HTTP client to request this path.
    Affected if The endpoint responds with HTTP 200 or other application responses, indicating the route exists and is active
  3. Identify if barcodeNo, barcode, or itemNo parameters are processed
    Review HTTP requests to the barcodeDetail endpoint. Check if any of these three parameters (barcodeNo, barcode, itemNo) are accepted as query string or POST body parameters.
    Affected if The application accepts and processes any of these three parameters without immediate rejection or sanitization feedback
  4. Inspect application logs for SQL error evidence
    Review application and database logs for SQL syntax errors, database error messages, or unusual query patterns when the affected parameters are used. Patterns like SQLSTATE, syntax error, or unterminated quotes indicate the vulnerability.
    Affected if Database errors appear in logs when malformed input is provided to the barcodeNo, barcode, or itemNo parameters, confirming unsanitized input reaches the database layer

A user is affected if they are running Zhilink ADP Application Developer Platform version 1.0.0 with the /adpweb/a/base/barcodeDetail/ endpoint accessible and accepting barcodeNo, barcode, or itemNo parameters 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

Implement parameterized queries or prepared statements for all database operations involving user-supplied input. Apply input validation and employ least-privilege database accounts to limit the impact of any successful injection.

Fix this in Adp Application Developer Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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