CVE-2026-15462: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in gingerplugins Sticky Chat Widget – Floating Chat Icons, Contact Form, Call, Click to Chat, Email & Message Buttons
The Sticky Chat Widget plugin for WordPress is vulnerable to SQL Injection via the 'scw_form_fields' parameter array keys of the 'scw_save_form_data' AJAX action in versions up to, and including, 1.4.2. This is due to the save_form_data() function passing attacker-controlled POST array keys unsanitized to $wpdb->insert(), which wraps column identifiers in backticks without escaping them, allowing a backtick in an attacker-supplied key to break out of the column-identifier list into raw SQL; additionally, the use of filter_input() bypasses WordPress's wp_magic_quotes() protection, and the widget_id validation loop is skipped entirely when no valid widget_id is supplied, leaving $isValid at 1. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
AI Analysis
Technical Summary
CVE-2026-15462 describes an SQL Injection vulnerability in the Sticky Chat Widget plugin for WordPress (versions <=1.4.2). The vulnerability is triggered via the 'scw_form_fields' parameter array keys in the 'scw_save_form_data' AJAX action. The save_form_data() function passes attacker-controlled POST array keys unsanitized to $wpdb->insert(), which wraps column identifiers in backticks without escaping backticks in keys. This allows attackers to break out of the column-identifier list and append arbitrary SQL queries. The use of filter_input() bypasses WordPress's wp_magic_quotes() protection, and the validation loop for widget_id is skipped if no valid widget_id is provided, leaving $isValid set to 1 and enabling unauthenticated exploitation to extract sensitive database information.
Potential Impact
An unauthenticated attacker can exploit this vulnerability to inject additional SQL queries into existing database operations, potentially extracting sensitive information from the WordPress database. The CVSS 3.1 base score is 7.5 (High), reflecting network attack vector, low attack complexity, no privileges required, no user interaction, and high confidentiality impact without integrity or availability impact.
Mitigation Recommendations
No official patch or fix is currently documented in the provided data. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict access to the vulnerable AJAX action if possible and monitor for suspicious activity related to the 'scw_save_form_data' AJAX endpoint. Avoid using affected versions (<=1.4.2) in production environments if feasible.
CVE-2026-15462: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in gingerplugins Sticky Chat Widget – Floating Chat Icons, Contact Form, Call, Click to Chat, Email & Message Buttons
Description
The Sticky Chat Widget plugin for WordPress is vulnerable to SQL Injection via the 'scw_form_fields' parameter array keys of the 'scw_save_form_data' AJAX action in versions up to, and including, 1.4.2. This is due to the save_form_data() function passing attacker-controlled POST array keys unsanitized to $wpdb->insert(), which wraps column identifiers in backticks without escaping them, allowing a backtick in an attacker-supplied key to break out of the column-identifier list into raw SQL; additionally, the use of filter_input() bypasses WordPress's wp_magic_quotes() protection, and the widget_id validation loop is skipped entirely when no valid widget_id is supplied, leaving $isValid at 1. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
CVSS v3.1
Score 7.5high
Affected software
gingerplugins
Sticky Chat Widget – Floating Chat Icons, Contact Form, Call, Click to Chat, Email & Message Buttons
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-15462 describes an SQL Injection vulnerability in the Sticky Chat Widget plugin for WordPress (versions <=1.4.2). The vulnerability is triggered via the 'scw_form_fields' parameter array keys in the 'scw_save_form_data' AJAX action. The save_form_data() function passes attacker-controlled POST array keys unsanitized to $wpdb->insert(), which wraps column identifiers in backticks without escaping backticks in keys. This allows attackers to break out of the column-identifier list and append arbitrary SQL queries. The use of filter_input() bypasses WordPress's wp_magic_quotes() protection, and the validation loop for widget_id is skipped if no valid widget_id is provided, leaving $isValid set to 1 and enabling unauthenticated exploitation to extract sensitive database information.
Potential Impact
An unauthenticated attacker can exploit this vulnerability to inject additional SQL queries into existing database operations, potentially extracting sensitive information from the WordPress database. The CVSS 3.1 base score is 7.5 (High), reflecting network attack vector, low attack complexity, no privileges required, no user interaction, and high confidentiality impact without integrity or availability impact.
Mitigation Recommendations
No official patch or fix is currently documented in the provided data. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict access to the vulnerable AJAX action if possible and monitor for suspicious activity related to the 'scw_save_form_data' AJAX endpoint. Avoid using affected versions (<=1.4.2) in production environments if feasible.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-07-10T20:14:05.080Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6aa379d691cc7f38489ada36
Added to database: 09/11/2026, 03:47:34 UTC
Last enriched: 09/11/2026, 04:02:19 UTC
Last updated: 09/11/2026, 22:23:26 UTC
Views: 17
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.