CVE-2025-13149 - Change Categories Plugin
CVE-2025-13149
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.
CVE-2025-13149
MEDIUM
CVSS 4.3
Published 2025-11-21
Updated 2025-11-21
AI Risk Elevated (72/100)
Active Exploit: Likely
Published Exploit: Public exploit references found
Priority: P3 Priority
Severity Band
MEDIUM
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Affected Components
1
Reference Links
2
AI Risk Engine
Elevated (72/100)
Exploitability
High
Active Exploitation
Likely
Published Exploit Status
Public exploit references found
AI Context
Machine-generated threat intelligence
AI
Updated 10 days ago
AI enriched 10 days ago (2026-04-09 08:48 UTC)
Technical Summary
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.
Potential Impact
Severity is MEDIUM (CVSS 4.3). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.
Exploitability Assessment
Exploitability is assessed as High based on published exploit references, remote code execution potential, low-bar exploit prerequisites.
Primary risk drivers: published exploit references, remote code execution potential, low-bar exploit prerequisites
Mitigation Recommendations
Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.
Detection & Monitoring
Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.
Business Impact Lens
Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.