HomeWordPress vulnerabilitiesGuest posting / Frontend Posting / Front Editor
Guest posting / Frontend Posting / Front Editor vulnerabilities
Guest posting / Frontend Posting / Front Editor has 6 known vulnerabilities in this database. The most recent published record is dated 22 Nov 2026.
- Known vulnerabilities
- 6
- Active installs
- 100+
- Latest version
- 5.0.6
- Last updated
- 16 Feb 2026
- Most recent
- 22 Nov 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-123068 | Not scored | Before 5.1.0 | Fixed in 5.1.0 | 16 h ago |
| Sensitive data exposure CVE-2026-1867 | Medium 5.9 | Before 5.0.6 | Fixed in 5.0.6 | 11 Mar 2026 |
| Broken access control CVE-2025-13419 | Medium 5.3 | Up to 5.0.0 | Fixed in a later version (latest 5.0.6) | 7 Jan 2026 |
| Open redirect CVE-2025-12569 | Medium 4.7 | Before 5.0.0 | Fixed in 5.0.0 | 24 Nov 2025 |
| Cross-site scripting (XSS) CVE-2024-2967 | Medium 4.4 | Up to 4.4.7 | Fixed in a later version (latest 5.0.6) | 2 May 2024 |
| Cross-site scripting (XSS) CVE-2023-1982 | Medium 4.8 | Up to 4.0.4 | Fixed in a later version (latest 5.0.6) | 30 Aug 2023 |
Read the published descriptions
- CVE-2026-123068, 22 Nov 2026
- The Front User Submit WordPress plugin before 5.1.0 does not validate the content of files uploaded through one of its unauthenticated endpoints and later serves them back with a Content-Type derived from the file's bytes and an inline disposition, allowing unauthenticated attackers to store an HTML or SVG payload and obtain a same-origin URL that executes arbitrary JavaScript in the browser of any user who opens it, including an administrator. CVE record
- CVE-2026-1867, 11 Mar 2026
- 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 record
- CVE-2025-13419, 7 Jan 2026
- 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. CVE record
- CVE-2025-12569, 24 Nov 2025
- 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 CVE record
- CVE-2024-2967, 2 May 2024
- 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. CVE record
- CVE-2023-1982, 30 Aug 2023
- The Front Editor WordPress plugin through 4.0.4 does not sanitize and escape some of its form settings, which could allow high-privilege users to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup) CVE record
What to do if you run Guest posting / Frontend Posting / Front Editor
If you run Guest posting / Frontend Posting / Front Editor, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Guest posting / Frontend Posting / Front Editor vulnerabilities
Free. We email you when a new vulnerability is published for Guest posting / Frontend Posting / Front Editor, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.