Security readout for executives and security teams
Plain-English summary
CVE-2022-27860 affects the WordPress Footer Text plugin through version 2.0.3. A tricked user could cause a site change that leads to script execution in visitors' browsers. Business impact is usually limited but can affect trust, site integrity, and users who interact with altered pages.
Executive priority
Handle in normal vulnerability remediation cadence, faster for public or high-traffic WordPress sites. Prioritize confirmation of plugin presence first; this CVE only matters where the specific Footer Text plugin is installed.
Technical view
The issue is CSRF leading to XSS in Shea Bunge's Footer Text WordPress plugin <= 2.0.3. CVSS 3.1 is 6.1 with network attack vector, low complexity, required user interaction, changed scope, and low confidentiality and integrity impact. No availability impact is listed.
Likely exposure
Exposure is limited to WordPress sites with Footer Text plugin version 2.0.3 or earlier installed. Risk depends on whether a relevant logged-in user can be induced to perform the unsafe action and whether the resulting script is rendered to users.
Exploitation context
The bundle does not show CISA KEV listing or any cited evidence of active exploitation. The reported path is social interaction plus CSRF resulting in XSS, not unauthenticated remote code execution.
Researcher notes
Evidence identifies the vulnerability class and affected version range but does not provide exploit details, active exploitation, or a named fixed version in the supplied bundle. Avoid assuming broader WordPress impact beyond this plugin.
Mitigation direction
- Inventory WordPress sites for the Footer Text plugin and installed version.
- Treat Footer Text <= 2.0.3 as vulnerable until vendor guidance says otherwise.
- Check WordPress.org and Patchstack for fixed versions or official remediation guidance.
- Disable or remove the plugin if no supported fixed version is available.
- Review recent footer content changes for unexpected scripts or injected markup.
Validation and detection
- Confirm whether Footer Text is installed on each WordPress site.
- Record the installed plugin version and compare it with <= 2.0.3.
- Check whether plugin settings or footer content contain unexpected HTML or scripts.
- Review web logs and WordPress audit logs for suspicious footer-setting changes.
- Verify remediation by confirming the plugin is updated, disabled, or removed.
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 lookupCWE-79: 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-27860 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
- Medium
- CVSS
- 6.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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:C/C:L/I:L/A:N2.82.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.1MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://wordpress.org/plugins/footer-text/CVE reference · x_refsource_CONFIRM
- https://patchstack.com/database/vulnerability/footer-text/wordpress-footer-text-plugin-2-0-3-cross-site-request-forgery-csrf-leading-to-cross-site-scripting-xss-vulnerabilityCVE reference · x_refsource_CONFIRM
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.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.