CVE-2026-15735
Received Received - Intake

Stored XSS in Contact Form to Any API WordPress Plugin

Publication date: 2026-07-29

Last updated on: 2026-07-29

Assigner: Wordfence

Description
The Contact Form to Any API plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'cf7anyapi_form_field' Post Meta in all versions up to, and including, 3.0.6 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-29
Last Modified
2026-07-29
Generated
2026-07-29
AI Q&A
2026-07-29
EPSS Evaluated
N/A
NVD
CVE-2026-15735
EUVD
EUVD-2026-50094

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
contact_form_to_any_api contact_form_to_any_api to 3.0.6 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a Stored Cross-Site Scripting (XSS) issue in the Contact Form to Any API WordPress plugin. It allows authenticated attackers with contributor-level access or higher to inject malicious scripts into web pages via insufficiently sanitized input in the 'cf7anyapi_form_field' Post Meta field. These scripts execute when users access the affected pages.

Detection Guidance

Check WordPress sites for the Contact Form to Any API plugin versions up to 3.0.6. Inspect pages for injected scripts via contributor-level access. Use security plugins to scan for stored XSS in post meta fields like 'cf7anyapi_form_field'.

Impact Analysis

If you use this WordPress plugin, attackers could steal user sessions, redirect to malicious sites, or deface your website. Users visiting your site might have their data compromised or be exposed to phishing attacks. The impact depends on the attacker's goals and the privileges of compromised accounts.

Compliance Impact

This vulnerability could lead to non-compliance with GDPR or HIPAA if user data is exposed or modified due to the XSS attack. GDPR requires protecting user data, and HIPAA mandates safeguarding protected health information. A breach could result in legal penalties or loss of trust.

Mitigation Strategies

Update the Contact Form to Any API plugin to the latest version. Remove unauthorized scripts from post meta fields. Restrict contributor-level access to trusted users. Implement web application firewalls to block XSS attempts.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-15735. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart