CVE-2023-38891
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 · uneditedSQL injection vulnerability in Vtiger CRM v.7.5.0 allows a remote authenticated attacker to escalate privileges via the getQueryColumnsList function in ReportRun.php.
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 confidenceSQL injection vulnerability in Vtiger CRM v7.5.0's getQueryColumnsList function in ReportRun.php allows a remote authenticated attacker to inject malicious SQL queries, potentially enabling privilege escalation through unauthorized database access.
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= 7.5.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Verify Vtiger CRM versionLocate the version file or check the About page in the Vtiger CRM admin interface. Common locations include config.php, version.php, or the Help > About section in the UI.Affected if The installed version is exactly 7.5.0
-
Locate ReportRun.php fileSearch for the ReportRun.php file in the CRM installation directory, typically under /modules/Reports/ or similar path based on your installation structure.Affected if The file exists and contains the getQueryColumnsList function
-
Confirm reporting module is accessibleCheck if the Reports module is enabled and accessible in Vtiger CRM. This can be verified through the admin panel under Module Manager or by attempting to access the Reports section.Affected if The Reports module is enabled and user can access reporting functionality
-
Verify authentication requirementConfirm that user authentication is configured and users can log into the CRM system. The SQL injection requires an authenticated session to exploit.Affected if User authentication is enabled and valid user credentials can be obtained
-
Inspect getQueryColumnsList functionExamine the ReportRun.php file for the getQueryColumnsList function. Look for direct use of user input in SQL queries without parameterized queries or input sanitization.Affected if The function uses unsanitized user input directly in SQL queries
You are affected if running Vtiger CRM version 7.5.0 with the Reports module enabled and the getQueryColumnsList function contains unsanitized SQL input.
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.
From vendor dataApply parameterized queries or prepared statements in the getQueryColumnsList function to sanitize user input, and update to the latest Vtiger CRM version if a patch is available.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-38891 — 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-38891 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