Vulnerability in Easy Post Submission (WordPress plugin) (CVE-2026-4431)
Summary
Vulnerability in Easy Post Submission (WordPress plugin) (CVE-2026-4431). Data can be tampered with by attackers. Exploitable via rbsm_submit_post.
Original description
The description as published by the source.
The Easy Post Submission plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the create_post() function in all versions up to, and including, 2.3.0. This is due to the rbsm_submit_post AJAX action being registered for unauthenticated users via wp_ajax_nopriv_rbsm_submit_post without any authorization checks when a postId parameter is supplied. This makes it possible for unauthenticated attackers to modify the title, content, excerpt, categories, and tags of arbitrary posts, as well as change the post status to draft (effectively unpublishing them) via the 'postId' parameter.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-4431 has been found in Easy Post Submission (WordPress plugin).
Attackers can target a specific entry point like rbsm_submit_post over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 9.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Easy Post Submission (WordPress plugin) CVE-2026-4431" on the vendor's site.
CVE-2026-4431 (Easy Post Submission (WordPress plugin)) — CWE-862 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: rbsm_submit_post / wp_ajax_nopriv_rbsm_submit_post / postId
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) exists in Easy Post Submission (WordPress plugin). Attackers reach the vulnerable code path via rbsm_submit_post without authentication.
Check the vendor advisory for the affected versions of Easy Post Submission (WordPress plugin). Attack surface: rbsm_submit_post / wp_ajax_nopriv_rbsm_submit_post / postId.
Severity: Critical (CVSS 9.1/10). Data can be tampered with by attackers.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Easy Post Submission (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web nvd.nist.gov
- web github.com