EUVD-2026-50198
GHSA-jqmh-vp8q-78mq
Severity by source
AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Unauthenticated network injection via public REST endpoint gives AV:N/AC:L/PR:N; payload runs in a different context (admin browser) giving S:C with low C/I, no availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
Lifecycle Timeline
2DescriptionCVE.org
The Database for CF7 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Array Form Field Values in all versions up to, and including, 1.2.6 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is exploitable by unauthenticated attackers because Contact Form 7 accepts array-structured input for ordinary text fields (e.g., your-name[]) via the public REST API endpoint /wp-json/contact-form-7/v1/contact-forms/{id}/feedback, and the plugin stores submitted data using $wpdb INSERT with serialize() into a custom wp_cf7db table, bypassing WordPress save-time filtering via wp_insert_post/wp_kses.
AnalysisAI
Stored cross-site scripting in the Database for CF7 WordPress plugin (all versions through 1.2.6) lets unauthenticated attackers persist arbitrary JavaScript that executes in the browser of any user who later views an affected page. The flaw is reachable through Contact Form 7's public REST feedback endpoint, which accepts array-structured field input that the plugin writes directly to its custom table without sanitization. No public exploit identified at time of analysis; issue reported by Wordfence and rated CVSS 7.2 with a scope change.
Technical ContextAI
The affected component is the Database for CF7 plugin (vendor code4life, CPE cpe:2.3:a:code4life:database_for_cf7), an add-on that captures and stores Contact Form 7 submissions in a custom wp_cf7db database table. The root cause is CWE-79 (improper neutralization of input during web page generation): the plugin ingests submission data via $wpdb->INSERT combined with serialize(), which deliberately bypasses the WordPress content-filtering path (wp_insert_post/wp_kses) that would normally sanitize stored content. Because Contact Form 7 accepts array-structured values for ordinary text fields (e.g. your-name[]) submitted to the REST API endpoint /wp-json/contact-form-7/v1/contact-forms/{id}/feedback, attacker-controlled array elements are stored verbatim and later rendered without output escaping. The referenced plugin source lines (database-for-cf7.php #L118 and #L236) correspond to the storage and rendering paths where sanitization and escaping are absent.
RemediationAI
No vendor-released patch identified at time of analysis - the supplied references point to Wordfence threat intelligence and to the plugin's trac source lines rather than a tagged fixed release, so no exact fix version can be cited. Until the vendor publishes a patched version above 1.2.6, the most reliable control is to deactivate and remove the Database for CF7 plugin, which stops the vulnerable storage/render path but disables persistence of form submissions. If the plugin must remain active, restrict or monitor the Contact Form 7 REST feedback endpoint (/wp-json/contact-form-7/v1/contact-forms/{id}/feedback) at the WAF or web-server layer to reject array-structured values for text fields and to filter script-bearing payloads, accepting that overly strict rules may break legitimate form submissions; deploy a WordPress security plugin (e.g. Wordfence) with XSS rules covering this issue; and avoid rendering stored submissions in privileged admin views until fixed. Monitor the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/07fda92e-a085-42c7-a16d-1eace1dee195?source=cve) for the patched release and upgrade promptly when available.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
Same weakness CWE-79 – Cross-site Scripting (XSS)
View allShare
External POC / Exploit Code
Leaving vuln.today