CVE-2025-13149 MEDIUM

CVE-2025-13149: Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories <= 4.9.1 - Authenticated (Author+) Missing Authorization to Post/Page Status Modification

Vendor Publishpress
Product Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories
Weakness CWE-862 · Missing authorization
Published November 21, 2025
Last update April 8, 2026

CVSS base score

4.3/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality None
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

What the vulnerability does

01Description

The Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories plugin for WordPress is vulnerable to unauthorized modification of data due to a missing authorization check on the "saveFutureActionData" function in all versions up to, and including, 4.9.1. This makes it possible for authenticated attackers, with author level access and above, to change the status of arbitrary posts and pages via the REST API endpoint.

Explanation of Vulnerability in Simple Terms

02Summary

The PublishPress Schedule Post Changes plugin for WordPress does not properly check user permissions before allowing logged-in users to modify post scheduling actions. A low-privileged user can change post status, delete, trash, or modify categories on scheduled posts without authorization. This affects versions up to 4.9.1.

What an attacker can do

03Attacker Capabilities

Modify or delete scheduled posts and change their status or categories without proper authorization.

Potential impact on your site

04Site Impact

Unauthorized users can alter or remove scheduled content, disrupting publishing workflows and potentially exposing or hiding posts.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege WordPress user account (e.g., contributor or subscriber role).

Key dates

06Disclosure timeline

November 21, 2025 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE