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-14718: CWE-862 Missing Authorization in publishpress Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories

0
Medium
VulnerabilityCVE-2025-14718cvecve-2025-14718cwe-862
Published: Fri Jan 09 2026 (01/09/2026, 06:34:54 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 plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.9.3. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with Contributor-level access and above, to create, update, delete, and publish malicious workflows that may automatically delete any post upon publication or update, including posts created by administrators.

AI-Powered Analysis

AILast updated: 01/09/2026, 06:58:10 UTC

Technical Analysis

CVE-2025-14718 is an authorization bypass vulnerability classified under CWE-862 affecting the WordPress plugin 'Schedule Post Changes With PublishPress Future' up to version 4.9.3. The plugin fails to properly verify whether a user is authorized to perform certain actions related to scheduling post changes, such as unpublishing, deleting, changing status, trashing, or modifying categories of posts. This flaw allows authenticated users with Contributor-level privileges or higher to create, update, delete, and publish malicious workflows that can automatically delete any post upon publication or update, including posts created by administrators. The vulnerability does not require user interaction beyond authentication and can be exploited remotely over the network. The CVSS v3.1 base score is 5.4 (medium), reflecting low attack complexity and privileges required but limited impact on confidentiality. The integrity and availability of WordPress content can be compromised, potentially leading to loss or unauthorized modification of critical posts. No patches or exploit code are currently publicly available, and no known active exploitation has been reported. The vulnerability is significant for organizations relying on PublishPress Future for content scheduling, especially those with multiple contributors who have Contributor-level access or above.

Potential Impact

For European organizations, this vulnerability poses a risk to the integrity and availability of WordPress-managed content. Attackers with Contributor-level access can delete or alter posts, potentially disrupting business communications, marketing content, or critical information published on corporate websites. This could lead to reputational damage, loss of customer trust, and operational disruptions. Organizations in sectors such as media, e-commerce, education, and government that rely heavily on WordPress for content management are particularly vulnerable. The ability to delete administrator-created posts elevates the threat, as it could result in the loss of important announcements or regulatory disclosures. Although confidentiality is not directly impacted, the integrity and availability issues could have cascading effects on business continuity and compliance with data governance policies under regulations like GDPR.

Mitigation Recommendations

1. Immediately restrict Contributor-level and higher access to trusted users only, minimizing the number of users who can exploit this vulnerability. 2. Monitor and audit all workflow changes and scheduled post modifications within the PublishPress Future plugin to detect suspicious activities. 3. Disable or uninstall the Schedule Post Changes With PublishPress Future plugin if it is not essential to reduce the attack surface. 4. Apply security hardening measures on WordPress installations, including limiting plugin installations and enforcing strict role-based access controls. 5. Regularly back up WordPress content and workflows to enable rapid restoration in case of malicious deletions. 6. Stay alert for official patches or updates from PublishPress and apply them promptly once available. 7. Use Web Application Firewalls (WAFs) with rules to detect and block abnormal API calls related to post scheduling and workflow management. 8. Educate content managers and administrators about the risks of elevated privileges and the importance of monitoring plugin activity.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-15T13:48:03.777Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6960a320ecefc3cd7c0b9826

Added to database: 1/9/2026, 6:41:36 AM

Last enriched: 1/9/2026, 6:58:10 AM

Last updated: 1/10/2026, 10:15:21 PM

Views: 10

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 in Console -> Billing for AI refresh and higher limits.

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

Latest Threats