CVE-2025-13741 MEDIUM

CVE-2025-13741: Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories <= 4.9.2 - Missing Authorization to Authenticated (Contributor+) Authors' Emails Exposure

Vendor Publishpress
Product Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories
Weakness CWE-862 · Missing authorization
Published December 16, 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 Low
Integrity None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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 access of data due to a missing capability check on the getAuthors function in all versions up to, and including, 4.9.2. This makes it possible for authenticated attackers, with Contributor-level access and above, to retrieve emails for all users with edit_posts capability.

Explanation of Vulnerability in Simple Terms

02Summary

The PublishPress Schedule Post Changes plugin for WordPress contains an authorization flaw that allows authenticated users with low privileges to read sensitive information they should not access. An attacker with a basic user account can view data that is normally restricted to higher-privilege roles. The vulnerability affects versions up to 4.9.2 and requires a valid WordPress login to exploit.

What an attacker can do

03Attacker Capabilities

Read sensitive information restricted to higher-privilege users.

Potential impact on your site

04Site Impact

Unauthorized information disclosure to any logged-in user, potentially exposing private post data or scheduling details.

Conditions required to exploit

05Prerequisites

Attacker must have a valid low-privilege WordPress user account.

Key dates

06Disclosure timeline

December 16, 2025 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE