CVE-2024-5808: The WP Ajax Contact Form WordPress plugin through 2.2.2 does not have CSRF check in place when deleting emails

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

wp ajax contact form: upgrade to newer than 2.2.2. Exact commands for each OS are on this page.

Q: Is CVE-2024-5808 being exploited?

CVE-2024-5808 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-5808 affect?

CVE-2024-5808 affects wp ajax contact form. Severity is medium (CVSS 4.3). The WP Ajax Contact Form WordPress plugin through 2.2.2 does not have CSRF check in place when deleting emails from the email list, which could allow attackers to make a logged in admin perform such action via a CSRF attack

Q: How urgent is CVE-2024-5808?

Priority 23/100. Public exploit reference

Routine

MEDIUM 4.3UPGRADE

CVE-2024-5808 is a medium-severity flaw (CVSS 4.3) affecting wp ajax contact form. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The WP Ajax Contact Form WordPress plugin through 2.2.2 does not have CSRF check in place when deleting emails from the email list, which could allow attackers to make a logged in admin perform such action via a CSRF attack

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.2% (top 88%)
CISA exploited list	No
Weakness	CWE-352
Published	2024-07-30
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: masdiblogs

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

Am I affected?

Timeline

2024-07-30 06:15 UTCPublished CVE record published
2026-06-17 08:16 UTCUpdated Record last modified

masdiblogs wp ajax contact form UPGRADE

Affected: <= 2.2.2

Fixed in: newer than 2.2.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wp-ajax-contact-form || rpm -q wp-ajax-contact-form || wp-ajax-contact-form --version

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

sudo apt update && sudo apt install --only-upgrade wp-ajax-contact-form

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wp-ajax-contact-form

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-5808?

wp ajax contact form: upgrade to newer than 2.2.2. Exact commands for each OS are on this page.

Is CVE-2024-5808 being exploited?

CVE-2024-5808 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-5808 affect?

CVE-2024-5808 affects wp ajax contact form. Severity is medium (CVSS 4.3). The WP Ajax Contact Form WordPress plugin through 2.2.2 does not have CSRF check in place when deleting emails from the email list, which could allow attackers to make a logged in admin perform such action via a CSRF attack

How urgent is CVE-2024-5808?

Priority 23/100. Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-5809 MEDIUM 6.1 UPGRADE The WP Ajax Contact Form WordPress plugin through 2.2.2 does not sanitise and escape a parameter before output

References

← Back to latest CVEs