Guest posting / Frontend Posting / Front Editor: A security weakness
Guest posting / Frontend Posting / Front Editor is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation.
- Component
- Guest posting / Frontend Posting / Front Editor
- Plugin slug
guest-posting-frontend-posting-front-editor- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Mar 11, 2026
This CVE was published Mar 11, 2026 and is one of 2 known issues for this plugin.
Update, patch or deactivate.
Update Guest posting / Frontend Posting / Front Editor to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The Guest posting / Frontend Posting / Front Editor WordPress plugin before 5.0.6 allows passing a URL parameter to regenerate a .json file based on demo data that it initially creates. If an administrator modifies the demo form and enables admin notifications in the Guest posting / Frontend Posting / Front Editor WordPress plugin before 5.0.6's settings, it is possible for an unauthenticated attacker to export and download all of the form data/settings, including the administrator's email address.
CVE / CNA vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N