Contact Form to Any API
contact-form-to-any-api · plugin
Known security vulnerabilities for Contact Form to Any API. Find out in seconds which version runs on your site with WP Lens.
6 known vulnerabilities
2 exploitable without logging in · latest Jul 28, 2026
Listed on wordpress.org · latest 3.0.7 · last updated Aug 6, 2026 · 8K+ installs
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- High 8.5
CVE-2024-30242login required≤ 1.1.8
WordPress Contact Form to Any API plugin <= 1.1.8 - Auth. SQL Injection vulnerability
- High 7.2
CVE-2023-32741high privilege≤ 1.1.2
WordPress Contact Form to Any API Plugin <= 1.1.2 is vulnerable to SQL Injection
- High 7.1
CVE-2026-39449unauthenticated · needs a click≤ 3.0.3
WordPress Contact Form to Any API plugin <= 3.0.3 - Cross Site Scripting (XSS) vulnerability
- Medium 6.4
CVE-2026-15735contributor+≤ 3.0.6
Contact Form to Any API <= 3.0.6 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'cf7anyapi_form_field' Post Meta
- Medium 6.1
CVE-2024-7617unauthenticated≤ 1.2.4
Contact Form to Any API <= 1.2.4 - Unauthenticated Stored Cross-Site Scripting via Contact Form
- Medium 4.3
CVE-2023-47871login required≤ 1.1.6
WordPress Contact Form to Any API plugin <= 1.1.6 - Broken Access Control vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).