Plugins · front-editor · data as of 2026-11-04
Is Guest posting / Frontend Posting / Front Editor safe? Known vulnerabilities and latest version
- Latest version
- 5.0.6
- Last updated
- 2026-02-16
- Active installs
- 100+
- Known issues on record
- 7
- Unpatched in latest
- 2
- Tested up to WP
- 6.9.11 · PHP 7.0+
This plugin enables users to submit post content from Front End. Use our plugin to implement guest posting — by aharonyan
What to do
- There is no fixed version yet. If you can live without Guest posting / Frontend Posting / Front Editor for now, deactivate it and delete it until the developer ships a fix.
- If you must keep it, limit who can log in (remove unused accounts, especially low-level ones) and put a web application firewall in front of the site.
- Watch for an update: get an email when this page changes.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.
With WP-CLI: wp plugin get front-editor --field=version shows what you run; wp plugin update front-editor updates it.
Check your version
Known vulnerabilities
7 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
medium 5.9 CVE-2026-1867 · published 2026-03-11
Information disclosure in Guest posting / Frontend Posting / Front Editor (older than 5.0.6)
- Affected
- older than 5.0.6
- Fixed in
- 5.0.6
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
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.
medium 5.3 CVE-2025-13419 · published 2026-01-07
Missing authorization check in Guest posting / Frontend Posting / Front Editor (5.0.0 and older)
- Affected
- 5.0.0 and older
- Fixed in
- 5.0.1 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Guest posting / Frontend Posting / Front Editor – WP Front User Submit plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the '/wp-json/bfe/v1/revert' REST API endpoint in all versions up to, and including, 5.0.0. This makes it possible for unauthenticated attackers to delete arbitrary media attachments.
medium 4.7 CVE-2025-12569 · published 2025-11-24
Open redirect in Guest posting / Frontend Posting / Front Editor (older than 5.0.0)
- Affected
- older than 5.0.0
- Fixed in
- 5.0.0
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
The Guest posting / Frontend Posting / Front Editor WordPress plugin before 5.0.0 does not validate a parameter before redirecting the user to its value, leading to an Open Redirect issue
high 7.1 CVE-2025-28988 · published 2025-06-27
Reflected cross-site scripting (XSS) in Guest posting / Frontend Posting / Front Editor (4.9.3 and older)
- Affected
- 4.9.3 and older
- Fixed in
- 4.9.4
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in aharonyan WP Front User Submit / Front Editor front-editor allows Reflected XSS.This issue affects WP Front User Submit / Front Editor: from n/a through <= 4.9.3.
high 7.1 affects latest 5.0.6 CVE-2025-52795 · published 2025-06-20
Cross-site request forgery (CSRF) in Guest posting / Frontend Posting / Front Editor (5.0.6 and older)
- Affected
- 5.0.6 and older
- Fixed in
- no fix listed yet
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Cross-Site Request Forgery (CSRF) vulnerability in aharonyan WP Front User Submit / Front Editor front-editor allows Cross Site Request Forgery.This issue affects WP Front User Submit / Front Editor: from n/a through <= 5.0.6.
medium 5.9 affects latest 5.0.6 CVE-2025-47617 · published 2025-05-07
Stored cross-site scripting (XSS) in Guest posting / Frontend Posting / Front Editor (5.0.6 and older)
- Affected
- 5.0.6 and older
- Fixed in
- no fix listed yet
- Access needed (per CVSS)
- Needs an admin-level account; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in aharonyan WP Front User Submit / Front Editor front-editor allows Stored XSS.This issue affects WP Front User Submit / Front Editor: from n/a through <= 5.0.6.
medium 4.4 CVE-2024-2967 · published 2024-05-02
Stored cross-site scripting (XSS) in Guest posting / Frontend Posting / Front Editor (4.4.7 and older)
- Affected
- 4.4.7 and older
- Fixed in
- 4.4.8 *
- Access needed (per CVSS)
- Needs an admin-level account
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Guest posting / Frontend Posting wordpress plugin – WP Front User Submit / Front Editor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via form settings in all versions up to, and including, 4.4.7 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.
NVD CVE-2024-2967Wordfence advisoryCode change (fix)wordpress.org
Recent activity
- 2026-02-16 — latest release on wordpress.org (5.0.6).
- 2026-03-11 — Information disclosure disclosed (CVE-2026-1867), fixed in 5.0.6.
- 2026-01-07 — Missing authorization check disclosed (CVE-2025-13419), fixed in 5.0.1.
- 2025-11-24 — Open redirect disclosed (CVE-2025-12569), fixed in 5.0.0.
Get an email when Guest posting / Frontend Posting / Front Editor has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Guest posting / Frontend Posting / Front Editor (front-editor) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Cross-site scripting (XSS) (3) · Sensitive data exposure (1) · Missing authorization (1) · Open redirect (1) · Cross-site request forgery (CSRF) (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/front-editor (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/front-editor"><img src="https://laskyr.com/plugins/front-editor/badge.svg" alt="Guest posting / Frontend Posting / Front Editor vulnerability status"></a>