The Frontend Dashboard WordPress plugin before 3.0.5, ProfileGrid WordPress plugin before 6.0.0.5 do not prevent an
Source GCVE Database
Not known to be exploited : upgrade to 3.0.5 soon.
Data as of 29 Oct 2026, 07:12 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 3.0.5, 6.0.0.5
Exploitation evidence
Disclosed: evidence found.
CVE published 29 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade Frontend Dashboard to 3.0.5; ProfileGrid to 6.0.0.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Frontend Dashboard | Affected
| Fixed in
|
| ProfileGrid | Affected
| Fixed in
|
AI-suggested
Upgrade the Frontend Dashboard WordPress plugin to version 3.0.5 or later and the ProfileGrid WordPress plugin to version 6.0.0.5 or later. These versions contain fixes that prevent unauthenticated users from injecting serialized PHP objects into user metadata. No other mitigation steps are indicated.
Description
The Frontend Dashboard WordPress plugin before version 3.0.5 and the ProfileGrid WordPress plugin before version 6.0.0.5 contain a vulnerability that allows unauthenticated users to store serialized PHP objects in user metadata. These objects are deserialized when a public profile is viewed, enabling PHP object injection that can lead to arbitrary file write and potential remote code execution.