PublishPress Statuses 1.3.7: Security Hardening and Editor Workflow Fixes

This post is about a release of the PublishPress Statuses plugin. WordPress provides only “Draft” and “Pending Review”. With this plugin, you can add new statuses and build real publishing workflows.

PublishPress Statuses 1.3.7 is an important maintenance and security update for teams that rely on custom publishing statuses. The biggest change is stronger protection around who can assign, change, and manage statuses, along with fixes that make the Approve button and editor screens behave more reliably.


Security and permission improvements

This release tightens status permissions across the main places where editors update content, so users should only be able to choose statuses they are allowed to use.

  • Status changes: Permission checks are stronger in the Block Editor, Classic Editor, Quick Edit, and across different post types.
  • Role manager compatibility: If another role management plugin denies a status permission, PublishPress Statuses now respects that denial.
  • Status settings: Managing status definitions is restricted to users with the right permissions.
  • Privacy statuses: Custom privacy status selection now has stricter authorization checks.
  • Safer editing screens: Issues that could allow unwanted scripts through page URL slug updates or status detail updates have been fixed.

Workflow fixes

Several fixes focus on making editorial workflows more predictable, especially when teams use custom roles or supplemental status permissions.

  • Approve button: The button now applies the selected status when a user has been granted status assignment access separately from their main role.
  • Roles tab: Administrator and Editor checkboxes now more consistently show the correct status assignment permissions.
  • Custom labels: Labels for built-in statuses now display more consistently.
  • Migration reliability: Older status data is handled more reliably when moving from previous PublishPress setups.

Editor performance and polish

  • Block Editor performance: Long editing sessions should use less unnecessary processing because repeated background checks no longer build up over time.
  • Classic Editor compatibility: Older script usage was updated to avoid deprecation warnings in Classic Editor screens.
  • Changelog formatting: The Free and Pro changelog introductions now display without an unwanted line break.

If your site uses PublishPress Statuses for editorial approvals, custom statuses, or role based publishing permissions, this is a recommended update because it strengthens security while fixing several practical workflow issues.

This post provides an overview of the new features in this release of the PublishPress Statuses plugin. The complete changelogs for both Free and Pro versions are available in our Docs area.

PublishPress Statuses
  • Steve Burge

    Steve is the founder of PublishPress. He's been working with open source software for over 20 years. Originally from the UK, he now lives in Sarasota in the USA. This profile is generated by the PublishPress Authors plugin.