dbcve.org
CWE-610Weakness · CWE-610

CVE-2026-12788

MEDIUM · 6.3 CVSS v3.1 Published 2026-06-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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 determined in zhilink 智互联(深圳)科技有限公司 ADP Application Developer Platform 应用开发者平台 1.0.0. This vulnerability affects unknown code of the file /adpweb/a/base/barcodeDetail/import of the component XML Parser. This manipulation causes xml external entity reference. It is possible to initiate the attack remotely. The exploit has been publicly disclosed and may be utilized. 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 · moderate confidence

The ADP Application Developer Platform version 1.0.0 contains an XML External Entity (XXE) injection vulnerability in the barcodeDetail/import functionality. The XML parser processes user-supplied XML without disabling external entity references, allowing attackers to inject malicious XML that can read local files, perform server-side request forgery (SSRF), or cause denial of service. This can be exploited remotely via crafted XML payloads sent to the affected endpoint.

MitigationDisable external entity processing and DTD processing in the XML parser configuration for the /adpweb/a/base/barcodeDetail/import endpoint. Implement strict input validation and use a secure XML parser that does not resolve external entities by default.

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

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

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 ADP Application Developer Platform installation and version
    Locate the application installation directory and check for version information in version files, manifest, or the application's main binary/dll properties. Typical locations include the root installation folder or WEB-INF directory for web applications.
    Affected if The installed version matches 1.0.0 or falls within an unspecified version range containing this release.
  2. Verify the barcodeDetail/import endpoint is exposed
    Check the application's routing configuration or web.xml file to confirm the endpoint /adpweb/a/base/barcodeDetail/import is registered and accessible. Use a web proxy or curl to send a GET request to this endpoint and observe the response.
    Affected if The endpoint responds with an XML upload or import form, indicating it accepts XML input.
  3. Inspect XML parser configuration for external entity settings
    Locate the XML parser configuration files used by the application. Search for XML parser initialization code in the application's source files, configuration files, or libraries that handle the barcodeDetail/import functionality. Look for parser settings such as 'external-general-entities', 'external-parameter-entities', 'dtd-support', or 'prohibit-dtd'.
    Affected if The XML parser is configured with external entity processing enabled (no explicit disabling of XXE vectors).
  4. Check for disabled secure XML parsing features
    Review the code or configuration that initializes the XML parser for the import endpoint. Verify whether the application explicitly sets security features like 'XMLConstants.FEATURE_SECURE_PROCESSING', disables DTD processing, or uses a safe XMLReader with external entities disabled.
    Affected if The application does not explicitly disable external entity processing or DTD processing in its XML parser configuration for this endpoint.
  5. Review application logs for XXE indicators
    Examine application server logs and access logs for the barcodeDetail/import endpoint. Look for errors related to XML parsing, file access attempts, or unusual XML payloads that might indicate exploitation attempts.
    Affected if Logs show XML parsing errors involving external entities or file references, suggesting the vulnerable parser is processing such requests.

The environment is affected if ADP Application Developer Platform version 1.0.0 is installed, the barcodeDetail/import endpoint is accessible, and the XML parser handling that endpoint does not explicitly disable external entity and DTD processing.

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

Disable external entity processing and DTD processing in the XML parser configuration for the /adpweb/a/base/barcodeDetail/import endpoint. Implement strict input validation and use a secure XML parser that does not resolve external entities by default.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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