LiveActive security incident?Get immediate response
CVE Record

CVE-2023-34005: WordPress Front End Users Plugin <= 3.2.24 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Etoile Web Design Front End Users plugin <= 3.2.24 versions.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A vulnerable WordPress plugin could let an attacker trick an authenticated site user into triggering an unwanted action through CSRF. The public record describes versions up to 3.2.24 of Etoile Web Design Front End Users. The CVSS vector indicates user interaction is required and the rated impact is availability, not data theft.

Executive priority

Treat this as a moderate WordPress plugin exposure. Prioritize internet-facing or business-critical WordPress sites first, especially where the plugin supports customer or member workflows. No active exploitation is cited in the provided sources, but unsupported vulnerable plugins should not remain deployed.

Technical view

CVE-2023-34005 is a CWE-352 CSRF issue in the WordPress Front End Users plugin, package front-end-only-users, affecting <=3.2.24 per the provided description. CVSS 3.1 score is 6.5 with network attack vector, low complexity, no privileges required, required user interaction, unchanged scope, and high availability impact.

Likely exposure

Exposure is likely limited to WordPress sites that have Etoile Web Design Front End Users installed at version 3.2.24 or earlier. The provided affected metadata is sparse, so confirm plugin identity and version directly from each WordPress instance.

Exploitation context

The source bundle does not indicate CISA KEV listing or active exploitation. Exploitation would require a victim interaction consistent with CSRF. The available records do not describe public exploit maturity, specific vulnerable actions, or confirmed real-world abuse.

Researcher notes

The public bundle identifies CSRF and CVSS impact but lacks endpoint-level details, fixed-version information, or exploit evidence. Validation should focus on asset inventory, plugin version confirmation, and vendor guidance rather than attempting reproduction against production systems.

Mitigation direction

  • Inventory WordPress sites for the front-end-only-users plugin.
  • Check vendor, WordPress.org, or Patchstack guidance for a fixed version.
  • Upgrade if a vendor-supported fixed release is available.
  • Disable or remove the plugin where business impact allows.
  • Restrict administrative access and reinforce user awareness around suspicious links.

Validation and detection

  • Confirm whether Front End Users is installed on each WordPress site.
  • Compare installed versions against the <=3.2.24 affected range.
  • Review vendor and Patchstack entries for current remediation guidance.
  • After any update or removal, regression-test affected user workflows.
  • Review site logs for unusual availability-impacting admin actions.
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-34005 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
6.5 (3.1)
Known Exploited
No
Published

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

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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2023-34005Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
Etoile Web DesignFront End Usersfront-end-only-users, 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.