LiveActive security incident?Get immediate response
CVE Record

CVE-2023-51407: WordPress Split Test For Elementor plugin <= 1.6.9 - Cross Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in Rocket Elements Split Test For Elementor.This issue affects Split Test For Elementor: from n/a through 1.6.9.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a CSRF issue in the WordPress Split Test For Elementor plugin through version 1.6.9. An attacker could trick a logged-in site user into causing an unintended plugin-related change. The public bundle does not identify the exact action affected or a confirmed fixed version.

Executive priority

Treat this as a medium-priority WordPress hygiene issue. It is not evidenced as actively exploited here, but it can affect site integrity if vulnerable plugin versions remain in use and privileged users are tricked.

Technical view

CVE-2023-51407 is CWE-352 affecting Rocket Elements Split Test For Elementor through 1.6.9. CVSS 3.1 is 4.3 with network attack vector, low complexity, no attacker privileges, required user interaction, and low integrity impact only.

Likely exposure

Exposure is limited to WordPress sites running the split-test-for-elementor plugin at version 1.6.9 or earlier. Risk is higher for sites with active administrators or editors who remain logged in while browsing external content.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Exploitation would require user interaction from a victim with an active WordPress session; the public details provided do not name the vulnerable request or business action.

Researcher notes

Available evidence is sparse: the bundle identifies CSRF, affected plugin range, CVSS vector, CWE, and Patchstack reference, but not the vulnerable endpoint, nonce behavior, affected action, or fixed release. Avoid assuming impact beyond low integrity.

Mitigation direction

  • Inventory WordPress sites for the split-test-for-elementor plugin.
  • Update the plugin if vendor guidance names a fixed version beyond 1.6.9.
  • Disable or remove the plugin where no fixed version is available.
  • Restrict administrator browsing from logged-in WordPress sessions.
  • Monitor vendor and Patchstack advisories for remediation details.

Validation and detection

  • Confirm whether split-test-for-elementor is installed on each WordPress site.
  • Record installed versions and flag 1.6.9 or earlier.
  • Review WordPress audit logs for unexpected plugin setting or content changes.
  • Verify whether a vendor-supported fixed release exists before closing remediation.
  • Document compensating controls if the plugin must remain enabled.
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-2023-51407 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-2023-51407Attack 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
Rocket ElementsSplit Test For Elementorsplit-test-for-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.