CVE-2026-13425 HIGH

CVE-2026-13425: Database for CF7 <= 1.2.6 - Unauthenticated Stored Cross-Site Scripting via Array Form Field Values

Vendor Code4Life
Product Database for CF7
Weakness CWE-79 · XSS
Published July 29, 2026
Last update July 29, 2026

CVSS base score

7.2/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

Database for CF7 versions up to 1.2.6 contain a cross-site scripting vulnerability that allows unauthenticated attackers to inject malicious scripts. The vulnerability affects the scope beyond the vulnerable component itself. No user interaction is required for exploitation. Site administrators should update to a version newer than 1.2.6.

What an attacker can do

03Attacker Capabilities

Inject malicious scripts that execute in visitors' browsers and affect other parts of the site.

Potential impact on your site

04Site Impact

Visitors' browsers could execute attacker-controlled scripts, potentially stealing data or redirecting users.

Conditions required to exploit

05Prerequisites

Network access only; no authentication or user interaction required.

Key dates

06Disclosure timeline

July 29, 2026 CVE published
July 29, 2026 Record updated

Related vulnerabilities

08Related CVE