Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-13741: CWE-862 Missing Authorization in publishpress Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories

0
Medium
VulnerabilityCVE-2025-13741cvecve-2025-13741cwe-862
Published: Tue Dec 16 2025 (12/16/2025, 11:15:44 UTC)
Source: CVE Database V5
Vendor/Project: publishpress
Product: Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories

Description

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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 10:16:06 UTC

Technical Analysis

CVE-2025-13741 is a vulnerability classified under CWE-862 (Missing Authorization) found in the WordPress plugin 'Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories.' The issue arises from the absence of a proper capability check in the getAuthors function, which is responsible for retrieving author-related data. This missing authorization allows any authenticated user with at least Contributor-level privileges to access email addresses of all users who have the edit_posts capability, which typically includes Editors and Administrators. The vulnerability affects all plugin versions up to and including 4.9.2. Exploitation requires authentication but no further user interaction, and it can be performed remotely via network access to the WordPress site. The CVSS v3.1 base score is 4.3, reflecting a medium severity level due to the limited scope of impact—only confidentiality is affected, with no impact on integrity or availability. No public exploits have been reported, but the exposure of email addresses can facilitate targeted phishing, social engineering, or further attacks against privileged users. The vulnerability underscores the importance of enforcing strict authorization checks on sensitive functions within WordPress plugins, especially those managing user data and content scheduling.

Potential Impact

The primary impact of CVE-2025-13741 is the unauthorized disclosure of email addresses belonging to users with elevated privileges (edit_posts capability) on WordPress sites using the affected PublishPress plugin. This breach of confidentiality can enable attackers to conduct targeted phishing campaigns, spear-phishing, or social engineering attacks against site administrators and editors, potentially leading to further compromise. Although the vulnerability does not allow direct modification or deletion of content, the exposure of sensitive user information undermines trust and may violate privacy regulations such as GDPR. Organizations relying on this plugin risk reputational damage and increased attack surface for subsequent intrusions. The medium severity rating reflects that exploitation requires authenticated access at Contributor level or higher, limiting the attacker base but still posing a significant risk in environments with multiple contributors or where contributor accounts may be compromised.

Mitigation Recommendations

To mitigate CVE-2025-13741, organizations should immediately update the 'Schedule Post Changes With PublishPress Future' plugin to a patched version once released by the vendor. In the absence of an official patch, administrators can implement the following measures: 1) Restrict Contributor-level user creation and monitor existing accounts for suspicious activity to reduce the risk of unauthorized exploitation. 2) Apply custom code or hooks to enforce capability checks on the getAuthors function, ensuring only authorized roles can access sensitive user data. 3) Limit access to the WordPress admin area via IP whitelisting or VPN to reduce exposure. 4) Monitor logs for unusual access patterns or attempts to enumerate user data. 5) Educate users about phishing risks, as exposed emails may be targeted. 6) Regularly audit installed plugins for security updates and remove unnecessary plugins to minimize attack surface. These targeted mitigations go beyond generic advice by focusing on access control hardening and proactive monitoring specific to this vulnerability.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-11-26T13:44:15.219Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 694144fdb7167ed5be7864d0

Added to database: 12/16/2025, 11:39:41 AM

Last enriched: 2/27/2026, 10:16:06 AM

Last updated: 3/24/2026, 10:40:43 AM

Views: 248

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses