dbcve.org
InjectionWeakness · CWE-74

CVE-2026-11456

HIGH · 7.3 CVSS v3.1 Published 2026-06-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/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
A vulnerability was identified in Chanjet CRM 1.0. This affects an unknown part of the file /tools/jxf_dump_systable.php of the component HTTP GET Request Handler. Such manipulation of the argument gblOrgID leads to sql injection. The attack may be launched remotely. The exploit is publicly available and might 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

SQL injection vulnerability in Chanjet CRM 1.0's /tools/jxf_dump_systable.php via the gblOrgID parameter in HTTP GET requests. Remote attackers can inject arbitrary SQL commands due to improper input validation.

MitigationRestrict network access to the affected endpoint, deploy WAF rules to detect SQL injection patterns in the gblOrgID parameter, and migrate to a supported CRM platform since the vendor did not respond to the disclosure.

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify if Chanjet CRM is installed
    Search for Chanjet CRM installation directories, check web server document roots for chanjet or crm-related folders, or review installed applications inventory
    Affected if Chanjet CRM 1.0 is present on the system
  2. Verify the vulnerable PHP file exists
    Check for the presence of /tools/jxf_dump_systable.php in the web application directory structure
    Affected if The file /tools/jxf_dump_systable.php exists in the web root
  3. Confirm the gblOrgID parameter is accepted
    Send a request to the endpoint with a test value: GET /tools/jxf_dump_systable.php?gblOrgID=test
    Affected if The application accepts and processes the gblOrgID parameter without returning an error or requiring authentication
  4. Check for SQL injection vulnerability
    Send a benign SQL injection test payload in the gblOrgID parameter, such as: GET /tools/jxf_dump_systable.php?gblOrgID=1' OR '1'='1
    Affected if The application returns unexpected database errors, different content than normal, or displays SQL syntax in error messages
  5. Verify no input sanitization is applied
    Review the jxf_dump_systable.php source code if accessible, looking for prepared statements, parameterized queries, or input validation functions applied to gblOrgID
    Affected if The code directly uses gblOrgID in SQL queries without sanitization or parameter binding

You are affected if Chanjet CRM 1.0 is installed and the /tools/jxf_dump_systable.php endpoint accepts the gblOrgID parameter without proper SQL injection protections.

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

Restrict network access to the affected endpoint, deploy WAF rules to detect SQL injection patterns in the gblOrgID parameter, and migrate to a supported CRM platform since the vendor did not respond to the disclosure.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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