WordPress security changelog
MEDIUM CVE-2025-13419 Deferred

Guest posting / Frontend Posting / Front Editor – WP Front User Submit: A security weakness

Guest posting / Frontend Posting / Front Editor – WP Front User Submit 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.

CVE / CNA score 5.3 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Guest posting / Frontend Posting / Front Editor – WP Front User Submit
Plugin slug
guest-posting-frontend-posting-front-editor-wp-front-user-submit
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Jan 07, 2026
Weakness
CWE-862 — Missing Authorization

This CVE was published Jan 07, 2026 and is one of 1 known issue for this plugin.

Update, patch or deactivate.

Update Guest posting / Frontend Posting / Front Editor – WP Front User Submit 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 – 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 / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Primary and upstream sources