Custom Post Status
Custom Post Status has one disclosed vulnerability in the WordSec catalog, all reported in 2025; it remains unpatched as of September 2026. Their average CVSS score is 4.3, and the most serious one scores 4.3 out of 10.
The most common weakness is Cross-Site Request Forgery (CSRF), behind 1 of the records (100%).
The one issue recorded for Custom Post Status has no published fix yet, which makes virtual patching the only reliable mitigation. The oldest unresolved one dates back to 2025.
All of these findings were reported by Skalucy. Custom Post Status is installed on roughly 40 WordPress sites, so each unpatched flaw has a wide blast radius. The current release is tested up to WordPress 4.5.33.
CVE-2025-68885Custom Post Status <= 1.1.0 - Cross-Site Request Forgery
Read the full analysisVulnerability Records
Custom Post Status
Author
page-carbajal
This project helps you implement your own Custom Status in the Post Submit Box. Implements register_post_status and a little jQuery function to render the status on the admin screen. This plugin is Open Source software. It was built with <3 in Cancun by Page Carbajal / Software Engineer. Requested and sponsored by Octopus / Agencia de Marketing Digital. At this time, all post status are private. All Posts you mark with your Custom Status will not be included in the LOOP unless the user is logged-in.
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C