CVE-2023-49954
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 · uneditedThe CRM Integration in 3CX before 18.0.9.23 and 20 before 20.0.0.1494 allows SQL Injection via a first name, search string, or email address.
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 confidenceThe CRM Integration component in 3CX phone system software versions prior to 18.0.9.23 and 20.0.0.1494 contains a SQL Injection vulnerability. The vulnerability stems from insufficient input validation on first name, search string, and email address parameters within the CRM integration feature. An unauthenticated attacker could inject malicious SQL statements through these fields to manipulate database queries, potentially enabling unauthorized data access, modification, or complete database compromise.
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< 18.0.9.23>= 20.0, < 20.0.0.1494CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify 3CX installation versionAccess the 3CX Management Console Dashboard or check the system information panel. The version is typically displayed on the main dashboard or in Help > About. Alternatively, check the installed software version through the system package manager or the 3CX installation directory if you have direct server access.Affected if The installed version is less than 18.0.9.23, or is 20.0.x but less than 20.0.0.1494
-
Confirm CRM Integration component is activeIn the 3CX Management Console, navigate to Settings > CRM Integration or look for CRM-related modules under the integration or settings sections. Verify whether any CRM integration (such as Salesforce, Microsoft Dynamics, or custom CRM) is configured and enabled.Affected if CRM Integration is enabled and accessible to unauthenticated or low-privilege users
-
Assess exposure of vulnerable parametersExamine the CRM integration web interface for search functionality that accepts first name, free-text search, or email address inputs. These parameters are where the SQL injection occurs. Check if these fields are reachable without authentication or through the public-facing 3CX web client.Affected if The first name field, search string field, or email address field in the CRM integration is accessible and accepts user-supplied input without sanitization
-
Review access controls on CRM endpointsCheck the URL paths used by the CRM integration feature (commonly under /crm or /api/crm). Determine if these endpoints are exposed to the internet or accessible to unauthenticated users by reviewing the web server configuration and firewall rules.Affected if The CRM integration endpoints are externally exposed or accessible to unauthenticated attackers
You are affected if your 3CX version is below 18.0.9.23 or falls between 20.0.0.0 and 20.0.0.1494, AND the CRM Integration component is enabled and its input fields (first name, search, email) are accessible to unauthenticated users.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped18.0.9.2320.0.0.1494
Apply the vendor-supplied patches by updating 3CX to version 18.0.9.23 or later, or version 20.0.0.1494 or later. As an interim control, restrict network access to the CRM integration interface and implement WAF rules to detect and block SQL injection attempts.
3CX version 18.0.9.23 or later for the 18.x branch; 3CX version 20.0.0.1494 or later for the 20.x branch
- 1. Back up the current 3CX configuration and all critical data before proceeding with the upgrade.
- 2. Identify the currently installed 3CX version by accessing the management console and navigating to the About section.
- 3. For 3CX versions in the 18.x branch: Upgrade to version 18.0.9.23 or later.
- 4. For 3CX versions in the 20.x branch: Upgrade to version 20.0.0.1494 or later.
- 5. Download the appropriate fixed version from the official 3CX website or the 3CX customer portal.
- 6. Apply the upgrade following 3CX's standard upgrade procedures documented in their administration manual.
- 7. After upgrade completion, verify the CRM Integration module is functioning correctly and test that SQL injection is no longer possible via first name, search string, or email address fields.
- 8. Confirm the installed version matches the target fixed version in the management console.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-49954 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-49954 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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