Description
The User Frontend WordPress plugin before 4.3.11 does not prevent user-supplied field values from being deserialized when a submitted post is reopened in its frontend editing form, allowing authenticated users with subscriber-level access and above to perform PHP Object Injection, which may lead to remote code execution when a suitable gadget chain is present on the site.
Published: 2026-09-02
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The User Frontend WordPress plugin fails to validate deserialization of user-supplied fields when an existing post is reopened in its frontend edit form. An authenticated subscriber or higher can submit crafted serialized data, triggering PHP Object Injection. This flaw is a form of deserialization of untrusted data (CWE‑502) that can lead to remote code execution if the site contains a suitable gadget chain. The vulnerability allows attackers to run arbitrary code on the server, compromising confidentiality, integrity, and availability.

Affected Systems

All WordPress sites that install the User Frontend plugin with a version older than 4.3.11 are affected. The issue applies to subscribers and roles above, as they can access the frontend post edit form. No other vendors or products are listed as impacted.

Risk and Exploitability

Although the CVSS score is not provided and EPSS is unavailable, the exploit requires an authenticated user and a gadget chain on the target. The vulnerability is listed as not in CISA KEV. If a suitable gadget chain exists, the risk is high; otherwise the potential impact remains moderate. The likely attack vector is through the web interface, limited to accounts with subscriber‑level access or higher.

Generated by OpenCVE AI on September 2, 2026 at 07:21 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade User Frontend to version 4.3.11 or later
  • Revoke the ability for subscriber roles to edit posts via the frontend by removing the relevant capability or disabling the edit form
  • Monitor the application logs and database for suspicious serialized payloads or unexpected code execution attempts

Generated by OpenCVE AI on September 2, 2026 at 07:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 02 Sep 2026 07:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-502
CWE-94

Wed, 02 Sep 2026 06:15:00 +0000

Type Values Removed Values Added
Description The User Frontend WordPress plugin before 4.3.11 does not prevent user-supplied field values from being deserialized when a submitted post is reopened in its frontend editing form, allowing authenticated users with subscriber-level access and above to perform PHP Object Injection, which may lead to remote code execution when a suitable gadget chain is present on the site.
Title WP User Frontend < 4.3.11 - Subscriber+ PHP Object Injection via Frontend Post Edit Form
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-09-02T06:00:17.511Z

Reserved: 2026-08-06T14:36:33.718Z

Link: CVE-2026-19116

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-02T06:17:16.643

Modified: 2026-09-02T06:17:16.643

Link: CVE-2026-19116

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-02T07:30:18Z

Weaknesses
  • CWE-502

    Deserialization of Untrusted Data

  • CWE-94

    Improper Control of Generation of Code ('Code Injection')