LiveActive security incident?Get immediate response
CVE Record

CVE-2022-40219: WordPress FavIcon Switcher plugin <= 1.2.11 - Cross-Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in SedLex FavIcon Switcher plugin <= 1.2.11 at WordPress allows plugin settings change.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-40219 affects the WordPress FavIcon Switcher plugin through version 1.2.11. The reported issue is CSRF, meaning plugin settings could be changed without an intended administrative action. Business impact appears limited to integrity and availability of site behavior, but affected settings and fixed-version evidence are not fully described in the provided sources.

Executive priority

Handle during normal vulnerability remediation cycles unless the plugin is internet-facing on high-value WordPress properties or settings changes could affect brand trust. Prioritize removal if the plugin is unused.

Technical view

The bundle describes CWE-352 in SedLex FavIcon Switcher for WordPress <= 1.2.11, allowing plugin settings change. CVSS 3.1 is 5.4: network reachable, low complexity, low privileges, unchanged scope, low integrity and availability impact, no confidentiality impact. No exploit method, affected endpoint, nonce behavior, or patch version is provided.

Likely exposure

Exposure is limited to WordPress sites with the FavIcon Switcher plugin installed at version 1.2.11 or earlier. Sites without this plugin are not affected based on the supplied sources.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. It also does not provide proof-of-concept details. Treat this as a plausible plugin configuration-integrity risk, not confirmed internet-scale exploitation.

Researcher notes

Key gaps remain: the provided sources do not name a vulnerable endpoint, required capability, fixed version, exploit status, or concrete mitigation. Validation should focus on confirming plugin presence, version, operational need, and vendor guidance before asserting closure.

Mitigation direction

  • Inventory WordPress sites for FavIcon Switcher and record installed versions.
  • If installed and unused, disable and remove the plugin.
  • If still needed, check WordPress.org and vendor/Patchstack guidance for a fixed release.
  • Restrict WordPress administrative access to trusted users until remediation is confirmed.
  • Monitor site appearance and plugin settings for unexpected changes.

Validation and detection

  • Confirm whether FavIcon Switcher is installed on each WordPress instance.
  • Verify installed plugin version is greater than 1.2.11 or otherwise vendor-approved.
  • Review WordPress admin users and recent plugin setting changes.
  • Check security monitoring for unexpected site favicon or plugin configuration changes.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
cve · low confidence lookup

CVE-2022-40219 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2022-40219Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SedLexFavIcon Switcher (WordPress plugin)<= 1.2.11Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

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.