# CVE-2026-132749: Vtiger CRM through 8.4.0 Blind SQL Injection via Reports advanced_filter


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-p244-6hxh-mjjg

## What is CVE-2026-132749?

CVE-2026-132749 is a high-severity vulnerability in Vtiger CRM, published on 18 Nov 2026. 

### Official description

Vtiger CRM through 8.4.0 contains a blind SQL injection vulnerability in ReportRun::generateAdvFilterSql() that allows authenticated low-privileged users to inject SQL via the bw comparator. Attackers can send a crafted advanced_filter parameter containing a single quote to the Reports getRecordsCount action to break out of BETWEEN literals and extract database contents.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-132749?


## How do I fix CVE-2026-132749?

No fix has been published for CVE-2026-132749 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-132749 being exploited?

There is no known exploitation of CVE-2026-132749 in the wild and no public exploit code.

Public exploit code:

- PoC for CVE-2026-132749 - Blind SQL Injection in Vtiger CRM Reports via the advanced_filter parameter. (github_poc): https://github.com/SHAHID-XT/CVE-2026-132749-Vtiger-CRM-Reports-SQLi

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-132749 and fix it if it is affected.

What it is: CVE-2026-132749 is a high-severity vulnerability in Vtiger CRM, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-132749 in the wild and no public exploit code.

Affected product: Vtiger CRM. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-132749/ (Markdown: https://insights.sbomify.com/CVE-2026-132749/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-132749
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-132749
- OSV: https://osv.dev/vulnerability/CVE-2026-132749

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-132749/
Summaries are generated and may contain mistakes; the official description above is the record.
