Chaty Pro subscribers can perform time-based blind SQL injection
Chaty Pro through 3.5.5 lets any authenticated user, including a Subscriber, submit a widget_id value that fetch_custom_field() in admin/class-admin-base.php concatenates directly into a numeric SQL context without $wpdb->prepare() or integer casting. The query executes before the function checks its nonce, so that later check does not protect the database operation. Time-based blind SQL injection can disclose sensitive WordPress database contents. The CNA record does not disclose the request endpoint or AJAX action, and the referenced upstream source is no longer publicly available.
- Component
- Chaty Pro
- Plugin slug
chaty-pro- Affected
- <= 3.5.5
- Safe version
> 3.5.5- Published
- Jul 28, 2026
This CVE was published Jul 28, 2026 and is one of 2 known issues for this plugin.
Update, patch or deactivate.
Update Chaty Pro to a release newer than 3.5.5. The CNA record identifies the affected boundary but does not name a fixed tag. Review low-privilege accounts and database or application logs for delayed or unusual widget-field requests, and rotate credentials if database contents may have been exposed.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The Chaty Pro plugin for WordPress is vulnerable to Authenticated Time-Based Blind SQL Injection in versions up to and including 3.5.5. This is due to the fetch_custom_field() function in admin/class-admin-base.php retrieving the widget_id POST parameter via filter_input(INPUT_POST, ...) and directly concatenating the value into a raw SQL query in a numeric context without using $wpdb->prepare() or any integer casting. Additionally, the nonce verification check is performed after the SQL query has already executed, providing no protection against the injection. This makes it possible for authenticated attackers with subscriber-level access and above to inject arbitrary SQL commands, potentially leading to unauthorized extraction of sensitive database contents including user credentials and configuration data.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N