LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47682: WordPress WP User Frontend plugin <= 3.6.5 - Authenticated Privilege Escalation vulnerability

Improper Privilege Management vulnerability in weDevs WP User Frontend allows Privilege Escalation.This issue affects WP User Frontend: from n/a through 3.6.5.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-47682 affects the WordPress WP User Frontend plugin through version 3.6.5. It is an authenticated privilege escalation issue, meaning a logged-in attacker with high privileges could gain improper control. Business urgency is high for WordPress sites using this plugin, especially where privileged accounts are widely shared or weakly governed.

Executive priority

Prioritize within the normal high-severity remediation window, faster for internet-facing WordPress sites or environments with many privileged users. Active exploitation is not confirmed in the provided sources.

Technical view

The CVE describes CWE-269 improper privilege management in weDevs WP User Frontend. CVSS 3.1 is 7.2: network reachable, low complexity, high privileges required, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impact. Sources identify affected versions as through 3.6.5.

Likely exposure

Exposure is limited to WordPress installations running WP User Frontend version 3.6.5 or earlier. The CVSS vector indicates exploitation requires an authenticated high-privilege account, reducing mass unauthenticated risk but increasing concern for compromised administrator-like accounts.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Treat this as a serious authenticated escalation risk, not as confirmed in-the-wild exploitation.

Researcher notes

Evidence is limited to the CVE metadata and Patchstack reference. The key constraints are PR:H and no UI, with full CIA impact. Do not assume unauthenticated exploitability or a specific fixed release unless confirmed from vendor or Patchstack details.

Mitigation direction

  • Inventory WordPress sites for WP User Frontend installations.
  • Confirm plugin versions and prioritize any version through 3.6.5.
  • Check weDevs and Patchstack guidance for the supported fixed version.
  • Disable or remove the plugin where safe until remediation is confirmed.
  • Review and restrict high-privilege WordPress accounts.

Validation and detection

  • Verify installed WP User Frontend version on each WordPress site.
  • Confirm no production site runs version 3.6.5 or earlier.
  • Review privileged WordPress accounts for unexpected users or role changes.
  • Check security logs for unusual authenticated administrative activity.
  • Document remediation status for each affected site.
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-269: 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
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-47682 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
High
CVSS
7.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2023-47682Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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
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-269 · source CWE mapping

Improper Privilege Management

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