HomeWordPress vulnerabilitiesDatabase for CF7
Database for CF7 vulnerabilities
Database for CF7 has 2 known vulnerabilities in this database. The most recent published record is dated 6 Oct 2026.
- Known vulnerabilities
- 2
- Active installs
- Not listed
- Latest version
- Unknown
- Last updated
- Unknown
- Most recent
- 6 Oct 2026
This plugin is shown as closed on WordPress.org, so check the vulnerability record and the developer's current information before deciding whether to keep it installed. WordPress.org reason: security issue.
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-39731 | High 7.1 | Up to 1.2.6 | No fix: plugin closed | 1 d ago |
| Cross-site scripting (XSS) CVE-2026-13425 | High 7.2 | Up to 1.2.6 | No fix: plugin closed | 29 Jul 2026 |
Read the published descriptions
- CVE-2026-39731, 6 Oct 2026
- Unauthenticated Cross Site Scripting (XSS) in Database for CF7 <= 1.2.6 versions. CVE record
- CVE-2026-13425, 29 Jul 2026
- 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. CVE record
What to do if you run Database for CF7
If you run Database for CF7, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Database for CF7 vulnerabilities
Free. We email you when a new vulnerability is published for Database for CF7, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.