Quick answers
- Is CVE-2026-103693 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-103693 being exploited in the wild.
- How severe is CVE-2026-103693?
- Informational severity, published 29 October 2026.
- Which products and versions are affected?
- Frontend Dashboard before 3.0.5; ProfileGrid before 6.0.0.5.
- Is there a fix for CVE-2026-103693?
- Yes: fixed in Frontend Dashboard 3.0.5; ProfileGrid 6.0.0.5. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-103693 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-103693?
- Check whether you run Frontend Dashboard or ProfileGrid at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Frontend Dashboard 3.0.5; ProfileGrid 6.0.0.5
Technical details
The Frontend Dashboard and ProfileGrid WordPress plugins fail to validate serialized PHP objects stored in user metadata before deserializing them during public profile viewing. An unauthenticated attacker can exploit this insecure deserialization (CWE-502) to inject arbitrary PHP objects, leading to arbitrary file writes and remote code execution. The vulnerability requires no authentication and can be triggered by viewing a public profile.
Affected products
- Frontend Dashboard Frontend Dashboard before 3.0.5
- ProfileGrid ProfileGrid before 6.0.0.5
Timeline
- 2026-10-27: disclosed
- 2026-10-29: advisory