SYS::ONLINE
Wasteland.
Briefs1714
Issues22
SinceFeb 2026
LIVE
⚡ Active KEV CVE-2026-4431 2026-08-05

Unauthenticated Post Tampering in WordPress "Easy Post Submission" (CVE-2026-4431)

"A missing capability check in the Easy Post Submission plugin for WordPress lets unauthenticated attackers rewrite or unpublish arbitrary posts on affected sites, earning a CVSS 3.1 score of 9.1 (Critical)."

A missing capability check in the Easy Post Submission plugin for WordPress lets unauthenticated attackers rewrite or unpublish arbitrary posts on affected sites, earning a CVSS 3.1 score of 9.1 (Critical).

What Is It

CVE-2026-4431 is a missing authorization flaw (CWE-862) in the create_post() function of the Easy Post Submission plugin for WordPress. The plugin registers the rbsm_submit_post AJAX action for unauthenticated users via wp_ajax_nopriv_rbsm_submit_post and performs no authorization checks when a postId parameter is supplied. The result is unauthorized modification of data by anyone who can reach the site.

The CVSS vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H, network-reachable, low complexity, no privileges, no user interaction, with high integrity and availability impact and no confidentiality impact.

Why It Matters

An unauthenticated attacker can modify the title, content, excerpt, categories, and tags of arbitrary posts; not just their own submissions. They can also flip a post's status to draft, effectively unpublishing it. That combination supports content defacement, injection of attacker-controlled text into trusted pages, and takedown of legitimate content, all without a login.

No CISA KEV entry was supplied for this CVE, so there is no confirmation of active exploitation in the wild at this time.

What's Vulnerable

Patch Status

The supplied record does not name a fixed version and includes no CISA KEV required action or due date. It does reference a WordPress plugin changeset (trunk revision 3488045, replacing 3427523) associated with the fix. Administrators running 2.3.0 or earlier should treat this as unpatched until a confirmed fixed release is verified, and consider disabling the plugin in the interim.

Sources