CVE-2022-3240: The "Follow Me Plugin" plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and

Q: How do I fix CVE-2022-3240?

follow me plugin: upgrade to newer than 3.1.1. Exact commands for each OS are on this page.

Q: Is CVE-2022-3240 being exploited?

CVE-2022-3240 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-2022-3240 affect?

CVE-2022-3240 affects follow me plugin. Severity is high (CVSS 8.8). The "Follow Me Plugin" plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.1.1. This is due to missing nonce validation on the FollowMeIgniteSocialMedia_options_page() function. This makes it

Q: How urgent is CVE-2022-3240?

Priority 48/100. High severity; Public exploit reference

This month

HIGH 8.8UPGRADE

CVE-2022-3240 is a high-severity flaw (CVSS 8.8) affecting follow me plugin. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The "Follow Me Plugin" plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.1.1. This is due to missing nonce validation on the FollowMeIgniteSocialMedia_options_page() function. This makes it possible for unauthenticated attackers to modify the plugin's settings and inject malicious JavaScript via a forged request granted they can trick a site administrator into performing an action such as clickin

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.6% (top 51%)
CISA exploited list	No
Weakness	CWE-352
Published	2022-11-15
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: follow me plugin project

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

Am I affected?

Timeline

2022-11-15 14:15 UTCPublished CVE record published
2026-06-17 04:59 UTCUpdated Record last modified

follow me plugin project follow me plugin UPGRADE

Affected: <= 3.1.1

Fixed in: newer than 3.1.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy follow-me-plugin || rpm -q follow-me-plugin || follow-me-plugin --version

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

sudo apt update && sudo apt install --only-upgrade follow-me-plugin

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade follow-me-plugin

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-2022-3240?

follow me plugin: upgrade to newer than 3.1.1. Exact commands for each OS are on this page.

Is CVE-2022-3240 being exploited?

CVE-2022-3240 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-2022-3240 affect?

CVE-2022-3240 affects follow me plugin. Severity is high (CVSS 8.8). The "Follow Me Plugin" plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.1.1. This is due to missing nonce validation on the FollowMeIgniteSocialMedia_options_page() function. This makes it

How urgent is CVE-2022-3240?

Priority 48/100. High severity; Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs