Dolibarr WhatsApp Module Blind SQL Injection Vulnerability (CVE-2026-76173)
Is it fixed? Not yet.
Ongoing since Nov 12, 10:17 UTC. First reported Nov 12, 10:17 UTC.
What happened
A high-severity blind SQL injection vulnerability exists in the public endpoint `public/webhook/receiver.php` of the WhatsApp module for Dolibarr 1.9. When the WHATSAPP_WEBHOOK_ALLOW option is enabled, an unauthenticated remote attacker can manipulate the `data.key.remoteJid` parameter to alter SQL queries via timing-based techniques.
What caused it?
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.
No verified workaround yet
None of the linked reports describe a mitigation. This page updates when one appears.
Official fixTimeline
- Investigating(current)
- Workaround available(upcoming)
- Resolved(upcoming)
- First report on security advisory
public endpoint `public/webhook/receiver.php` of the WhatsApp module for Dolibarr: CVE-2026-76173 (High)
Source
Evidence
1 report · 1 CVEShow
- [1]CVE First reportpublic endpoint `public/webhook/receiver.php` of the WhatsApp module for Dolibarr: CVE-2026-76173 (High)(opens security advisory in a new tab)
High severity. 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…
by Tenable 0upvotes 0comments
FAQ
What happened in the PHP issue?
A high-severity blind SQL injection vulnerability exists in the public endpoint `public/webhook/receiver.php` of the WhatsApp module for Dolibarr 1.9. When the WHATSAPP_WEBHOOK_ALLOW option is enabled, an unauthenticated remote attacker can manipulate the `data.key.remoteJid` parameter to alter SQL queries via timing-based techniques.
What is affected by the PHP issue?
PHP (versions: 1.9).
When did the PHP issue start and end?
It started Nov 12, 10:17 UTC and is still ongoing (6 d 18 h so far). This page updates as it develops.
How do I get alerts for PHP?
Subscribe to the PHP RSS feed for every new PHP incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether PHP is down. PHP feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.