# CVE-2026-103693: Frontend Dashboard < 3.0.5 and ProfileGrid < 6.0.0.5 - Unauthenticated PHP Object Injection


- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-qp7c-fqj4-fv88

## What is CVE-2026-103693?

CVE-2026-103693 is a critical vulnerability in Unknown Frontend Dashboard, published on 29 Oct 2026. 

### Official description

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.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2026-103693?


## How do I fix CVE-2026-103693?

No fix has been published for CVE-2026-103693 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-103693 being exploited?

There is no known exploitation of CVE-2026-103693 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-103693 and fix it if it is affected.

What it is: CVE-2026-103693 is a critical vulnerability in Unknown Frontend Dashboard, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-103693 in the wild and no public exploit code.

Affected product: Unknown Frontend Dashboard. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-103693/ (Markdown: https://insights.sbomify.com/CVE-2026-103693/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-103693
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-103693
- OSV: https://osv.dev/vulnerability/CVE-2026-103693

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-103693/
Summaries are generated and may contain mistakes; the official description above is the record.