Skip to main content
Vulnerability Database/CVE-2026-114120

CVE-2026-114120: SchedulePress Authorization Bypass Flaw

CVE-2026-114120 is an authorization bypass flaw in SchedulePress that allows Contributor-level users to modify post statuses and publish dates. This post explains the technical details, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-114120 Overview

CVE-2026-114120 is a missing authorization vulnerability [CWE-862] in the SchedulePress WordPress plugin (also known as WP Scheduled Posts) in versions before 5.3.5. The wpsp_el_editor_form AJAX action does not verify that the requesting user has rights to publish the target post. An authenticated Contributor-level attacker can reuse the wpsp-el-editor nonce from the Elementor modal to change post status and publish dates for posts owned by other users, including administrators. This enables unpublishing or rescheduling of administrator content and the publication of other users' pending or draft posts.

Critical Impact

Contributor-level accounts can modify the publication status and schedule of posts they do not own, breaking editorial controls across the site.

Affected Products

  • SchedulePress (WP Scheduled Posts) WordPress plugin versions prior to 5.3.5
  • WordPress sites using SchedulePress with the Elementor integration enabled
  • Any site allowing Contributor-level registration with the vulnerable plugin installed

Discovery Timeline

  • 2026-10-21 - CVE-2026-114120 published to NVD
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-114120

Vulnerability Analysis

The flaw resides in the wpsp_el_editor_form AJAX handler defined in includes/Admin.php of the WP Scheduled Posts plugin. The handler validates the wpsp-el-editor nonce but does not confirm that the current user can edit or publish the specific post identified by the request. Because the nonce is global to the Elementor modal rather than tied to a specific post ID, any authenticated user who can load the modal, including Contributors, can obtain a valid nonce and submit arbitrary post IDs with modified status and schedule parameters.

The handler also accepts any value for post_status, allowing a Contributor to force posts into states beyond future or publish. The result is a broken access control condition where editorial workflow enforcement is bypassed at the AJAX layer.

Root Cause

The root cause is a missing per-post capability check [CWE-862]. The code relied on nonce verification alone, treating a valid nonce as proof of authorization. WordPress nonces confirm request intent, not permission, so the handler must additionally call current_user_can('edit_post', $id) and current_user_can('publish_post', $id) for the target post. The vulnerable version did neither.

Attack Vector

An attacker with a Contributor account logs into the WordPress site and extracts the wpsp-el-editor nonce from the Elementor editor interface. The attacker then submits an authenticated AJAX request to admin-ajax.php with action=wpsp_el_editor_form, specifying an arbitrary post ID owned by another user along with a chosen post_status and schedule date. The server executes the status change without verifying ownership or publish rights.

php
                'wpsp_el_pinterest_board' => [],
            ]);

+            // The nonce is not tied to a post, so check the user may publish this one.
+            if (!empty($args['id']) && (!current_user_can('edit_post', absint($args['id'])) || !current_user_can('publish_post', absint($args['id'])))) {
+                wp_send_json_error([
+                    'msg' => __('You do not have permission to publish this post.', 'wp-scheduled-posts')
+                ], 403);
+            }
+
+            // The modal only schedules or publishes; ignore any other posted status.
+            if (!in_array($args['post_status'], ['future', 'publish'], true)) {
+                $args['post_status'] = 'future';
+            }
+
            do_action('wpsp_el_action_before', $args);

Source: GitHub WP Scheduled Posts Commit 0e7af0f — the patch adds the missing capability checks and constrains post_status to future or publish.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-114120

Indicators of Compromise

  • POST requests to wp-admin/admin-ajax.php with action=wpsp_el_editor_form originating from Contributor accounts.
  • Unexpected changes to post_status or post_date on posts owned by administrators or editors.
  • Previously scheduled or draft posts appearing as published without a corresponding entry in the audit log for an authorized user.
  • Published posts reverting to draft or future state without administrator action.

Detection Strategies

  • Review WordPress database wp_posts entries for post_modified timestamps that do not match the post_author activity history.
  • Correlate web server access logs for wpsp_el_editor_form AJAX calls against the role of the authenticated session.
  • Enable WordPress audit logging plugins to capture status transitions and compare the acting user against the post owner.

Monitoring Recommendations

  • Alert on any AJAX call to wpsp_el_editor_form where the authenticated user does not have the publish_posts capability.
  • Monitor for bulk post status changes within short time windows, which may indicate scripted abuse.
  • Baseline normal editorial activity per role and flag deviations where Contributors trigger scheduling or publishing actions.

How to Mitigate CVE-2026-114120

Immediate Actions Required

  • Upgrade SchedulePress (WP Scheduled Posts) to version 5.3.5 or later immediately via the WordPress plugin updater.
  • Audit recently modified posts and restore any that were improperly rescheduled, unpublished, or published by Contributor accounts.
  • Review the Contributor user list and remove accounts that are not required for current editorial work.

Patch Information

The vendor patch is available in commit 0e7af0f of the WPDevelopers/wp-scheduled-posts repository and ships in version 5.3.5. The fix adds current_user_can('edit_post', $id) and current_user_can('publish_post', $id) checks in both includes/Admin.php and includes/API/PostPanel.php, and constrains post_status to future or publish. See the GitHub commit, VulnCheck advisory, and the WordPress plugin page.

The REST route update in PostPanel.php replaces the generic permission_callback with a dedicated publish_permission_check:

php
         register_rest_route( $namespace, '/update-settings/(?P<post_id>\d+)', [
             'methods'             => \WP_REST_Server::CREATABLE,
             'callback'            => [ $this, 'publish_immediately' ],
-            'permission_callback' => [ $this, 'permission_check' ],
+            'permission_callback' => [ $this, 'publish_permission_check' ],
             'args'                => [
                 'post_id' => [
                     'required'          => true,

Source: GitHub WP Scheduled Posts Commit 0e7af0f.

Workarounds

  • Deactivate the SchedulePress plugin until the update to 5.3.5 can be applied.
  • Restrict Contributor-level account creation and disable open user registration where business requirements allow.
  • Block requests to admin-ajax.php with action=wpsp_el_editor_form at the WAF layer for sessions lacking the publish_posts capability.
bash
# Update the plugin via WP-CLI
wp plugin update wp-scheduled-posts --version=5.3.5

# Verify the installed version
wp plugin get wp-scheduled-posts --field=version

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.