Security readout for executives and security teams
Plain-English summary
CVE-2026-24364 affects the WordPress WP User Frontend plugin through version 4.2.5. It is a broken access control issue that could let an authenticated user perform actions they should not be allowed to perform. The main risk is unauthorized data or site-state changes, not data theft or outage based on the published CVSS.
Executive priority
Treat as a normal-priority WordPress remediation for sites allowing user accounts or frontend submissions. Prioritize higher for public membership, marketplace, publishing, or customer-portal sites where low-privileged users exist. There is no source-backed evidence of active exploitation.
Technical view
The CVE describes CWE-862 Missing Authorization in weDevs WP User Frontend, package wp-user-frontend, affecting versions through 4.2.5. CVSS 3.1 is 6.5: network exploitable, low complexity, low privileges required, no user interaction, unchanged scope, high integrity impact, no confidentiality or availability impact.
Likely exposure
Exposure is limited to WordPress sites running WP User Frontend version 4.2.5 or earlier. Exploitation requires a logged-in user account, according to the CVSS privileges-required value. Public sources do not identify specific roles, endpoints, or configurations required.
Exploitation context
No active exploitation is reported in the provided sources, and the CVE is not listed as KEV. The vulnerability is still business-relevant because authenticated users may be able to bypass intended authorization controls and make unauthorized changes.
Researcher notes
The public bundle does not provide endpoint-level details, proof-of-concept material, fixed-version data, or role-specific impact. Analysis should focus on authorization checks around WP User Frontend actions, but avoid assuming exploitability beyond authenticated access and high integrity impact stated in CVSS.
Mitigation direction
- Inventory WordPress sites for the WP User Frontend plugin.
- Identify installations running WP User Frontend version 4.2.5 or earlier.
- Check weDevs, WordPress.org, and Patchstack guidance for a fixed version or workaround.
- Upgrade the plugin if a vendor-supported fixed release is available.
- Restrict untrusted user registration or access until remediation is confirmed.
Validation and detection
- Confirm plugin presence and version in WordPress administration or asset inventory.
- Review user roles that can access WP User Frontend functionality.
- Check vendor or Patchstack advisories for fixed-version details.
- After updating, verify the installed plugin version is no longer affected.
- Review logs for unusual authenticated actions affecting posts, profiles, or frontend submissions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2026-24364 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N2.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.