LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32485: WordPress WP User Frontend plugin <= 4.2.8 - Broken Access Control vulnerability

Missing Authorization vulnerability in weDevs WP User Frontend wp-user-frontend allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP User Frontend: from n/a through <= 4.2.8.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-32485 is a high-severity access-control flaw in the WordPress WP User Frontend plugin. Public data says versions through 4.2.8 are affected. An unauthenticated remote attacker may be able to perform actions they should not be allowed to perform, creating business risk around unauthorized site changes or data integrity.

Executive priority

Treat this as a priority WordPress plugin exposure review. The issue can affect site integrity without attacker login, but public sources provided do not confirm active exploitation or name a fixed release.

Technical view

The issue is classified as missing authorization, CWE-862, in weDevs WP User Frontend package wp-user-frontend. CVSS 3.1 is 7.5: network exploitable, low complexity, no privileges, no user interaction, with high integrity impact and no stated confidentiality or availability impact.

Likely exposure

Exposure is limited to WordPress sites running WP User Frontend versions up to and including 4.2.8. The source bundle does not identify affected configurations beyond the plugin and version range.

Exploitation context

The CVE is not listed as KEV in the provided data, and no cited source states active exploitation. The CVSS vector indicates the flaw is remotely reachable without authentication or user interaction, increasing urgency for exposed WordPress sites.

Researcher notes

Evidence is currently sparse. Patchstack and CVE data identify missing authorization in WP User Frontend through 4.2.8, but do not provide exploit details, affected endpoints, or a named fixed version in the supplied sources.

Mitigation direction

  • Inventory WordPress sites for the WP User Frontend plugin.
  • Identify any installations running version 4.2.8 or earlier.
  • Check weDevs and Patchstack guidance for a fixed version or vendor mitigation.
  • Prioritize remediation for internet-facing and business-critical WordPress sites.
  • Restrict administrative and publishing workflows where possible until remediation is confirmed.

Validation and detection

  • Confirm plugin name, slug, and version on each WordPress instance.
  • Compare installed versions against the affected range: through 4.2.8.
  • Review site audit logs for unauthorized content, profile, or workflow changes.
  • Verify remediation by confirming the installed version is no longer affected per vendor guidance.
  • Document any compensating controls applied while awaiting vendor guidance.
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-2026-32485 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.5 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-32485Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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