Contact Form to Any API at a glance
- 8 publicly disclosed vulnerabilities, 5 of them rated High or Critical. The most recent was disclosed on Nov 20, 2026.
- Ranked #2363 by popularity on WordPress.org (8,000+ active installs).
- The latest version is 3.0.8 (released Nov 19, 2026). The most recent security fix shipped in 3.0.8.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your Contact Form to Any API version
Enter the Contact Form to Any API version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “Contact Form to Any API”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Contact Form to Any API”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (3.0.8). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known Contact Form to Any API vulnerabilities
Contact Form to Any API <= 3.0.7 - Unauthenticated Stored Cross-Site Scripting via CF7 Form Field Submissions
Cross-site scripting (XSS) · CVE-2026-131822
Affected versions: ≤ 3.0.7
Fixed in: 3.0.8
Severity: High 7.2 · Disclosed Nov 20, 2026
Contact Form to Any API <= 3.0.6 - Unauthenticated Sensitive File Disclosure
Other weakness · CVE-2026-18946
Affected versions: ≤ 3.0.6
Fixed in: 3.0.7
Severity: Medium 5.3 · Disclosed Aug 6, 2026
Contact Form to Any API <= 3.0.6 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'cf7anyapi_form_field' Post Meta
Cross-site scripting (XSS) · CVE-2026-15735
Affected versions: ≤ 3.0.6
Fixed in: 3.0.7
Severity: Medium 6.4 · Disclosed Jul 28, 2026
Contact Form to Any API <= 3.0.3 - Unauthenticated Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2026-39449
Affected versions: ≤ 3.0.3
Fixed in: 3.0.4
Severity: High 7.2 · Disclosed Apr 22, 2026
Contact Form to Any API <= 1.2.4 - Unauthenticated Stored Cross-Site Scripting via Contact Form
Cross-site scripting (XSS) · CVE-2024-7617
Affected versions: ≤ 1.2.4
Fixed in: 1.2.5
Severity: High 7.2 · Disclosed Sep 24, 2024
Contact Form to Any API <= 1.1.8 - Authenticated (Subscriber+) SQL Injection
SQL injection · CVE-2024-30242
Affected versions: ≤ 1.1.8
Fixed in: 1.1.9
Severity: Critical 9.9 · Disclosed Mar 26, 2024
Contact Form to Any API <= 1.1.6 - Missing Authorization via delete_cf7_records()
Missing authorization · CVE-2023-47871
Affected versions: ≤ 1.1.6
Fixed in: 1.1.7
Severity: Medium 6.5 · Disclosed Nov 20, 2023
Contact Form to Any API <= 1.1.2 - Authenticated (Administrator+) SQL Injection via 'form_id'
SQL injection · CVE-2023-32741
Affected versions: ≤ 1.1.2
Fixed in: 1.1.3
Severity: High 7.2 · Disclosed Jul 17, 2023
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| Contact Form to Any API <= 3.0.7 - Unauthenticated Stored Cross-Site Scripting via CF7 Form Field SubmissionsCross-site scripting (XSS) · CVE-2026-131822 | ≤ 3.0.7 | 3.0.8 | High 7.2 | Nov 20, 2026 |
| Contact Form to Any API <= 3.0.6 - Unauthenticated Sensitive File DisclosureOther weakness · CVE-2026-18946 | ≤ 3.0.6 | 3.0.7 | Medium 5.3 | Aug 6, 2026 |
| Contact Form to Any API <= 3.0.6 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'cf7anyapi_form_field' Post MetaCross-site scripting (XSS) · CVE-2026-15735 | ≤ 3.0.6 | 3.0.7 | Medium 6.4 | Jul 28, 2026 |
| Contact Form to Any API <= 3.0.3 - Unauthenticated Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2026-39449 | ≤ 3.0.3 | 3.0.4 | High 7.2 | Apr 22, 2026 |
| Contact Form to Any API <= 1.2.4 - Unauthenticated Stored Cross-Site Scripting via Contact FormCross-site scripting (XSS) · CVE-2024-7617 | ≤ 1.2.4 | 1.2.5 | High 7.2 | Sep 24, 2024 |
| Contact Form to Any API <= 1.1.8 - Authenticated (Subscriber+) SQL InjectionSQL injection · CVE-2024-30242 | ≤ 1.1.8 | 1.1.9 | Critical 9.9 | Mar 26, 2024 |
| Contact Form to Any API <= 1.1.6 - Missing Authorization via delete_cf7_records()Missing authorization · CVE-2023-47871 | ≤ 1.1.6 | 1.1.7 | Medium 6.5 | Nov 20, 2023 |
| Contact Form to Any API <= 1.1.2 - Authenticated (Administrator+) SQL Injection via 'form_id'SQL injection · CVE-2023-32741 | ≤ 1.1.2 | 1.1.3 | High 7.2 | Jul 17, 2023 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Nov 20, 2026.
Most common weaknesses in Contact Form to Any API
Cross-site scripting (XSS)
4 issues
An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.
SQL injection
2 issues
Input such as a form field can be used to rewrite the queries the site sends to its database. Attackers use it to pull out customer, member or order data.
Missing authorization
1 issue
Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.
Frequently asked questions
Is Contact Form to Any API safe to use?
Contact Form to Any API is a well-known plugin with 8,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (3.0.8) and turn on automatic updates.
How do I find which version of Contact Form to Any API my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.
← All plugin vulnerabilitiesContact Form to Any API on WordPress.org