Security readout for executives and security teams
Plain-English summary
A vulnerable WordPress plugin settings page could be changed through a tricked administrator. If successful, an attacker could add JavaScript to the site, potentially stealing data or acting as the administrator in visitors' browsers. The issue requires administrator interaction, but the reported CVSS is high because successful XSS can have broad site impact.
Executive priority
Treat this as a high-priority WordPress exposure check, especially on public or revenue-generating sites. The main business risk is site compromise through administrator-targeted social engineering and injected script. Prioritize inventory, version confirmation, and removal or remediation of affected installations.
Technical view
CVE-2022-3240 is a CSRF vulnerability in Follow Me Plugin for WordPress up to and including 3.1.1. The cited cause is missing nonce validation in FollowMeIgniteSocialMedia_options_page(), allowing unauthenticated attackers to alter plugin settings and inject JavaScript if an administrator is induced to perform an action.
Likely exposure
Exposure is limited to WordPress sites running the Follow Me Plugin, reportedly through version 3.1.1. The source bundle has inconsistent structured affected-version metadata, so defenders should confirm actual installed plugin name, slug, and version before scoping impact.
Exploitation context
The bundle does not show CISA KEV listing or any cited confirmation of active exploitation. Exploitation requires administrator interaction, such as following a malicious link, and results from a forged request changing plugin settings rather than direct unauthenticated code execution.
Researcher notes
The technical root cause is missing nonce validation on a plugin options handler. The supplied sources support CSRF leading to stored XSS through settings modification, but they do not provide a confirmed patch level, active exploitation evidence, or complete affected-version metadata beyond the narrative description.
Mitigation direction
- Identify all WordPress sites using Follow Me Plugin.
- Check vendor, WordPress.org, and Wordfence guidance for a fixed version.
- Disable or remove the plugin where it is unnecessary or cannot be confirmed fixed.
- Restrict administrator browsing and use separate accounts for WordPress administration.
- Review plugin settings for unexpected script content.
Validation and detection
- Inventory installed WordPress plugins and confirm Follow Me Plugin versions.
- Compare installed versions against the reported affected range through 3.1.1.
- Review plugin configuration for unauthorized JavaScript or unfamiliar links.
- Check administrator activity around suspicious setting changes.
- Confirm whether security controls block CSRF-driven setting changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-3240 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/25fab7b3-59ce-44ca-83fa-bd25b7f31af0?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/follow-me/trunk/follow-me.php#L261CVE reference
- https://www.wordfence.com/vulnerability-advisories-continued/#CVE-2022-3240CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.