WordPress Pixel Form BuilderPlugin & Autoresponder plugin <= 1.0.2 - SQL Injection Vulnerability

The SQL Injection vulnerability in Pixel WordPress Form BuilderPlugin & Autoresponder allows an attacker to bypass security measures and directly interact with the underlying database. Because it is a blind SQL injection, the attacker must infer the data by observing the application's response to various SQL queries. This can be a time-consuming process, but successful exploitation could lead to the extraction of sensitive user data, including usernames, passwords, email addresses, and form submissions. Depending on the database schema, an attacker might also be able to modify or delete data, potentially disrupting the website's functionality or causing data loss. The impact is particularly severe for websites that handle sensitive user information.

Websites utilizing the Pixel WordPress Form BuilderPlugin & Autoresponder, particularly those handling sensitive user data like e-commerce sites, membership platforms, or any form that collects personal information, are at significant risk. Shared hosting environments where multiple websites share the same database are also at increased risk, as a compromise of one site could potentially lead to the compromise of others.

• wordpress / composer / npm:

grep -r "pixel-formbuilder" /var/www/html/wp-content/plugins/

• wordpress / composer / npm:

wp plugin list | grep pixel-formbuilder

• wordpress / composer / npm:

curl -I https://your-wordpress-site.com/wp-content/plugins/pixel-formbuilder/ | grep SQL

1. 2025-05-23Disclosure

   disclosure

1. आरक्षित2025-04-01
2. प्रकाशित2025-05-23
3. संशोधित2026-04-28
4. EPSS अद्यतन2026-03-23

The primary mitigation for CVE-2025-31914 is to immediately upgrade the Pixel WordPress Form BuilderPlugin & Autoresponder to version 1.0.3 or later. If upgrading is not immediately feasible due to compatibility issues or testing requirements, consider implementing a Web Application Firewall (WAF) rule to filter out potentially malicious SQL injection attempts targeting the vulnerable endpoints. Specifically, look for patterns associated with SQL injection payloads in user input. Monitor database logs for unusual activity or error messages that might indicate an ongoing attack. Regularly review and sanitize all user inputs to prevent future injection vulnerabilities.