CVE-2024-7617: The Contact Form to Any API plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Contact Form

Q: How do I fix CVE-2024-7617?

contact form to any api: upgrade to newer than 1.2.2. Exact commands for each OS are on this page.

Q: Is CVE-2024-7617 being exploited?

CVE-2024-7617 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-7617 affect?

CVE-2024-7617 affects contact form to any api. Severity is high (CVSS 7.2). The Contact Form to Any API plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Contact Form 7 form fields in all versions up to, and including, 1.2.4 due to insufficient input sanitization and output escaping. This makes

Q: How urgent is CVE-2024-7617?

Priority 43/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.2REMOTEUPGRADE

CVE-2024-7617 is a high-severity flaw (CVSS 7.2) affecting contact form to any api. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Contact Form to Any API plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Contact Form 7 form fields in all versions up to, and including, 1.2.4 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.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.2 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.6% (top 51%)
CISA exploited list	No
Weakness	CWE-79
Published	2024-09-25
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: itpathsolutions

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-09-25 03:15 UTCPublished CVE record published
2026-06-17 08:20 UTCUpdated Record last modified

itpathsolutions contact form to any api UPGRADE

Affected: <= 1.2.2

Fixed in: newer than 1.2.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy contact-form-to-any-api || rpm -q contact-form-to-any-api || contact-form-to-any-api --version

2. UPGRADE to newer than 1.2.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade contact-form-to-any-api

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade contact-form-to-any-api

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-7617?

contact form to any api: upgrade to newer than 1.2.2. Exact commands for each OS are on this page.

Is CVE-2024-7617 being exploited?

CVE-2024-7617 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-7617 affect?

CVE-2024-7617 affects contact form to any api. Severity is high (CVSS 7.2). The Contact Form to Any API plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Contact Form 7 form fields in all versions up to, and including, 1.2.4 due to insufficient input sanitization and output escaping. This makes

How urgent is CVE-2024-7617?

Priority 43/100. High severity; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2023-32741 HIGH 7.6 UPGRADE Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in IT Path

References

← Back to latest CVEs