Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister or submit profile data unauthenticated
-
DeliveryStore serialized PHP object in user metadata
-
ExploitPublic profile view triggers deserialization
-
ExecutionPHP object injection fires gadget chain
-
ImpactArbitrary file write / potential RCE on host
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V1 - Encoding and Sanitization Safe deserialization, type allowlists
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the plugin's frontend user-registration/profile feature accept and persist attacker-supplied metadata from an unauthenticated user, and that the resulting public profile be viewable so the stored value is deserialized on view - both are default behaviors of these profile/membership plugins per the description. The confirmed impact is arbitrary file write; full remote code execution is described as 'potential', which for PHP object injection depends on a usable POP gadget chain being reachable in the loaded code - the available sources do not detail the exact trigger or which gadgets are required (consistent with the AC:H rating). Limiting factors: no authentication is needed (PR:N), but a public profile must actually be rendered to trigger deserialization, and reaching RCE rather than file write alone is not guaranteed by the sources. |
| Impact | This is a genuine high-priority issue, not an inflated CVSS score. The provided CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H, base 9.0) indicates network-reachable, unauthenticated exploitation with total impact and a scope change, consistent with CWE-502 PHP object injection leading to arbitrary file write and potential RCE. The vuln.today decision label is act_now and a vendor patch is available, reinforcing urgency. However, the signals are not all aligned: CISA SSVC records Exploitation as 'none' and Automatable as 'no' (while Technical Impact is 'total'), and there is no KEV listing, so there is no evidence of active exploitation in the wild. No EPSS score was supplied, so statistical exploitation probability cannot be weighed. The PoC is a reference only and is not verified as working exploit code. The AC:H metric signals non-trivial exploitation (object injection typically requires a usable POP gadget chain to reach RCE), but the available sources do not describe the trigger mechanism in detail, so the precise difficulty is unverified. Net: treat as a priority to patch promptly given unauthenticated reach, total technical impact, and the act_now label, while recognizing that automated mass exploitation is not currently indicated by SSVC. |
| Exploit ScenarioDerived | An unauthenticated attacker uses the plugin's frontend registration/profile functionality to store a crafted serialized PHP object in their user metadata. When that user's public profile is subsequently viewed, the stored data is deserialized, triggering PHP object injection that can write arbitrary files and potentially achieve remote code execution on the host. A public PoC reference exists (WPScan); it is not verified as working exploit code, and the AC:H rating reflects that successful code execution depends on conditions not detailed in the available sources. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 29, 2026
PHP object injection in the Frontend Dashboard WordPress plugin before 3.0.5 and the ProfileGrid WordPress plugin before 6.0.0.5 allows unauthenticated visitors to store a serialized PHP object in user metadata, which is then deserialized when a public profile is viewed. The confirmed impact is arbitrary file write, with remote code execution described as potential and dependent on a usable POP gadget chain being reachable in the loaded code; the CVSS vector (AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H, 9.0) reflects the high attack complexity of that chain rather than any authentication barrier. No active exploitation is confirmed by the available sources (SSVC Exploitation: none), and a public PoC reference exists but is not verified as working exploit code.
RemediationAI
Vendor-released patch: update Frontend Dashboard to 3.0.5 and ProfileGrid to 6.0.0.5. Both fixed versions are listed by the vendor and in EUVD, and the WPScan advisory at https://wpscan.com/vulnerability/c156065f-76f1-4f44-bc57-b7d57560813f/ covers the disclosure; sites running either plugin below those versions should treat the update as the primary and complete fix, with the priority label for this issue set to act_now. Where an immediate update of both plugins is not possible, the available sources do not document a specific configuration workaround, so the practical interim measures are limited to reducing exposure of the deserialization sink - for example by restricting or disabling public profile rendering and frontend user registration until the plugins are patched - with the trade-off that these are core features of the membership/profile functionality and disabling them may break site workflows. Combined with the file-write impact, hosting-level controls such as restricting write permissions on plugin and theme directories limit post-exploitation options but do not remove the underlying object injection.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-502, deserialization of untrusted data. Both plugins expose frontend user-registration and profile features that persist attacker-supplied values into WordPress user metadata without ensuring the data cannot carry a serialized PHP object; when a public profile containing that metadata is rendered, the stored string is passed to PHP's deserialization machinery. Successful object injection requires a POP gadget chain reachable within the loaded plugin and theme code - which is why the assessed vector carries AC:H - and the chain's capabilities determine whether the outcome stops at arbitrary file write or extends to remote code execution. The scope change (S:C) reflects that the vulnerable component can affect resources beyond its own security scope once file write is achieved on the WordPress host. The available sources do not detail the exact trigger path or which specific gadgets are required.
Know when Frontend Dashboard gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
Unauthenticated network-reachable storage of the payload gives AV:N/PR:N/UI:N; AC:H reflects the gadget-chain dependency to reach code execution; deserialization escaping the app context yields S:C with full C/I/A impact.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
3DescriptionCVE.org
The Frontend Dashboard WordPress plugin before 3.0.5, ProfileGrid WordPress plugin before 6.0.0.5 do not prevent an unauthenticated user from storing a serialized PHP object in user metadata that is deserialized when a public profile is viewed, allowing PHP object injection that can lead to arbitrary file write and potential remote code execution.
Articles & Coverage 1
Technical POC Analysis
The bug is CWE-502: Deserialization of Untrusted Data, specifically PHP object injection.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
Critical unauthenticated PHP object injection vulnerabilities in the Frontend Dashboard and ProfileGrid WordPress plugins allow attackers to write arbitrary files to the server, with potential for remote code execution. This impacts any organization hosting these plugins, risking full site compromise and data breach. Leadership should prioritize immediate patching due to the ease of exploitation and severe consequences.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Insecure deserialization occurs when an application converts serialized data (a stream of bytes representing an object's state) back into a living object without proper validation.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
More in Frontend Dashboard
View allPrivilege escalation in the WordPress plugin Frontend Dashboard (M A Vinoth Kumar), affecting versions through 3.0.7, le
The Frontend Dashboard plugin for WordPress is vulnerable to unauthorized code execution due to insufficient filtering o
Authenticated users with subscriber-level privileges can delete the Frontend Dashboard WordPress plugin's configured pro
EUVD-2026-112616
GHSA-qp7c-fqj4-fv88
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB