LiveActive security incident?Get immediate response
CVE Record

CVE-2023-45002: WordPress WP User Frontend plugin <= 3.6.8 - Broken Access Control vulnerability

Missing Authorization vulnerability in weDevs WP User Frontend allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP User Frontend: from n/a through 3.6.8.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-45002 is a broken access-control issue in the weDevs WP User Frontend WordPress plugin through version 3.6.8. A logged-in low-privilege user may be able to perform an action they should not be authorized to perform. The published impact is limited to integrity, not data disclosure or service outage.

Executive priority

Prioritize remediation on externally reachable WordPress sites that allow user registration or many low-privilege accounts. This is not currently evidenced as actively exploited in the supplied sources, but it can affect website integrity and should be handled in normal vulnerability management cycles.

Technical view

The sources describe CWE-862 missing authorization in WP User Frontend through 3.6.8. CVSS 3.1 is 4.3: network reachable, low complexity, low privileges required, no user interaction, unchanged scope, low integrity impact, and no confidentiality or availability impact.

Likely exposure

Exposure is limited to WordPress sites running the WP User Frontend plugin through 3.6.8, especially where untrusted or lightly trusted users can authenticate. Sites without the plugin, or not on affected versions, are not indicated as affected by the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Because the vector requires low privileges, risk is higher on sites with public registration, customer portals, contributors, or other broad authenticated-user populations.

Researcher notes

The public data does not specify the exact unauthorized action or a fixed version in the provided bundle. Treat the issue as a missing-authorization flaw affecting integrity only, and avoid assuming broader impact without vendor or Patchstack details.

Mitigation direction

  • Identify WordPress sites running WP User Frontend.
  • Check whether installed versions are 3.6.8 or earlier.
  • Follow weDevs or Patchstack guidance for upgrade, disablement, or other vendor-supported mitigation.
  • Limit untrusted account creation until exposure is resolved.
  • Review role permissions for WP User Frontend workflows.

Validation and detection

  • Inventory active WordPress plugins across production and staging.
  • Confirm WP User Frontend version and activation status.
  • Check whether public or customer self-registration is enabled.
  • Review audit logs for unexpected changes by low-privilege users.
  • Validate authorization controls using safe, non-destructive authenticated tests.
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-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-45002 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:L/UI:N/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:L/UI:N/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-45002Attack 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: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
weDevsWP User Frontendwp-user-frontend, n/aunaffected
Weakness

CWE details

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

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.