LiveActive security incident?Get immediate response
CVE Record

CVE-2022-47169: WordPress Visibility Logic for Elementor Plugin <= 2.3.4 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in StaxWP Visibility Logic for Elementor plugin <= 2.3.4 versions.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a medium-severity CSRF issue in the WordPress Visibility Logic for Elementor plugin through version 2.3.4. It may let an attacker trick a logged-in site user into causing an unintended change. The source bundle does not describe data theft, service disruption, or active exploitation.

Executive priority

Treat this as a routine but real WordPress hygiene item. It is not evidenced as actively exploited, but outdated plugins can create avoidable site integrity risk. Prioritize internet-facing or business-critical WordPress sites first.

Technical view

CVE-2022-47169 is CWE-352 affecting StaxWP Visibility Logic for Elementor <= 2.3.4. CVSS 3.1 is 4.3, with network reachability, low complexity, no attacker privileges, required user interaction, and low integrity impact. The public bundle does not identify the exact state-changing action or a named fixed version.

Likely exposure

Exposure is limited to WordPress sites running the Visibility Logic for Elementor plugin at version 2.3.4 or earlier. Sites not using this plugin are not indicated as affected by the supplied sources.

Exploitation context

The CVE is not listed in CISA KEV, and the supplied sources do not report active exploitation. Exploitation requires user interaction, consistent with CSRF, but the bundle does not provide enough detail to assess real-world exploitation patterns.

Researcher notes

The source bundle confirms CSRF, affected plugin, affected threshold, CWE-352, and CVSS. It does not describe the vulnerable endpoint, nonce behavior, required victim role, fixed version, exploit maturity, or precise impact beyond low integrity.

Mitigation direction

  • Inventory WordPress sites for the visibility-logic-elementor plugin and version.
  • Update to a vendor-supported version newer than 2.3.4 if available.
  • If no supported update exists, consult StaxWP or Patchstack guidance.
  • Remove or disable the plugin where it is not business-critical.
  • Limit privileged WordPress access to trusted users and managed devices.

Validation and detection

  • Confirm whether each WordPress site has Visibility Logic for Elementor installed.
  • Record installed plugin versions and flag versions 2.3.4 or earlier.
  • Check vendor or Patchstack advisories for fixed-release guidance.
  • Review change history for unexpected plugin or page visibility modifications.
  • Document unaffected systems where the plugin is absent.
Prepared
Confidence
medium
Sources
3

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-47169 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
4.3 (3.1)
Known Exploited
No
Published

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

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
2Source 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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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
StaxWPVisibility Logic for Elementorvisibility-logic-elementor, n/aunaffected
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.