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

AILast updated: 12/16/2025, 11:47:50 UTC

Technical Analysis

CVE-2025-13741 is a vulnerability classified under CWE-862 (Missing Authorization) affecting the WordPress plugin 'Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories' in all versions up to and including 4.9.2. The root cause is a missing capability check in the getAuthors function, which is responsible for retrieving author information. This flaw 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 is exploitable remotely without user interaction and requires only low privileges, making it easier to exploit within compromised or multi-user WordPress environments. The CVSS v3.1 score is 4.3 (medium severity), reflecting limited impact confined to confidentiality with no effect on integrity or availability. No patches or fixes are currently linked, and no known exploits have been reported in the wild. The exposure of email addresses can facilitate targeted phishing, social engineering, or further attacks against privileged users. This vulnerability highlights the importance of proper authorization checks in WordPress plugins, especially those managing content publishing workflows.

Potential Impact

For European organizations, the primary impact is the unauthorized disclosure of email addresses belonging to users with elevated privileges (edit_posts capability). This can lead to increased risk of spear-phishing campaigns, social engineering attacks, and potential lateral movement if attackers leverage exposed emails to gain further access. Organizations relying on WordPress for content management, especially media companies, educational institutions, and government agencies, may face reputational damage and privacy compliance issues under GDPR due to unauthorized exposure of personal data. Although the vulnerability does not directly compromise system integrity or availability, the indirect consequences of targeted attacks enabled by this data leak can be significant. The ease of exploitation by low-privileged users increases the risk in environments with multiple contributors or editors. Since no known exploits are currently in the wild, proactive mitigation is critical to prevent future abuse.

Mitigation Recommendations

European organizations should immediately audit their WordPress installations for the presence of the affected PublishPress Future plugin and verify the version in use. Until an official patch is released, consider temporarily disabling or removing the plugin to eliminate the vulnerability. If disabling is not feasible, restrict Contributor-level user accounts and review user roles to minimize exposure. Implement strict access controls and monitor logs for unusual access patterns to the getAuthors function or related API endpoints. Employ web application firewalls (WAFs) with custom rules to detect and block suspicious requests targeting this plugin’s functions. Additionally, educate content contributors about phishing risks and enforce multi-factor authentication (MFA) for users with edit_posts capabilities to mitigate risks from potential phishing attacks. Regularly check for updates from the vendor and apply patches promptly once available. Finally, conduct periodic security assessments of WordPress plugins to identify similar authorization issues proactively.

Need more detailed analysis?Get 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: 12/16/2025, 11:47:50 AM

Last updated: 12/16/2025, 8:18:11 PM

Views: 22

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats