CVE-2026-86827

BackWPup 3.3 - 5.7.6 - Unauthenticated Backup Job Execution via wp-cron.php

Published Oct 8, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
The BackWPup WordPress plugin before 5.7.7 does not verify that a request to its cron-triggered backup execution handler actually originates from WordPress's internal scheduled-event dispatch, allowing unauthenticated attackers to force any existing backup job to run immediately, independent of its configured trigger type or schedule.

Analysis

AI-generated

Technical impact

The BackWPup plugin for WordPress before version 5.7.7 fails to verify that a request sent to its cron‑triggered backup handler originates from WordPress’s internal scheduled‑event system. As a result, any attacker who can reach the wp‑cron.php endpoint can force any existing backup job to run immediately, regardless of its configured trigger type or schedule. This bypass of internal authentication allows unauthenticated users to trigger privileged backup operations, potentially impacting confidentiality, integrity, or availability of backups and site data.

Affected Systems

WordPress sites using the BackWPup plugin from version 3.3 through 5.7.6 are affected. The vulnerability is present in all builds within this range, irrespective of site configuration or other plugins.

Risk and Exploitability

The vulnerability can be exploited remotely via a simple HTTP request to wp‑cron.php without requiring authentication, making it an unauthenticated attack vector. The CVSS score of 5.3 indicates moderate severity. The exploit presents a moderate risk: it allows arbitrary, immediate initiation of backup jobs which can lead to data leakage, unintended modification of backup settings, or resource exhaustion. The EPSS score is very low (< 1 %), and the issue is not listed in the CISA KEV catalog. Because the attack only needs a web request, the likelihood of exploitation depends largely on whether the site is publicly accessible and whether the wp‑cron.php endpoint is exposed.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade BackWPup to version 5.7.7 or later
  • Restrict access to the wp‑cron.php endpoint at the web server level (e.g., using .htaccess or firewall rules) so that only trusted IPs or the WordPress process can invoke it
  • Disable or secure external calls to the cron system by using a non‑cached cron implementation or by configuring the site to run WP‑cron jobs internally

Generated by OpenCVE AI on October 8, 2026 at 17:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Wordpress-extensions
Wordpress-extensions backwpup
Vendors & Products Wordpress-extensions
Wordpress-extensions backwpup
Type Values Removed Values Added
Weaknesses CWE-287
Type Values Removed Values Added
Weaknesses CWE-862
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-287
Type Values Removed Values Added
Description The BackWPup WordPress plugin before 5.7.7 does not verify that a request to its cron-triggered backup execution handler actually originates from WordPress's internal scheduled-event dispatch, allowing unauthenticated attackers to force any existing backup job to run immediately, independent of its configured trigger type or schedule.
Title BackWPup 3.3 - 5.7.6 - Unauthenticated Backup Job Execution via wp-cron.php
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
WPScan
Published
Updated
Oct 8, 2026, 10:59 AM
Reserved
Sep 8, 2026, 2:25 PM
Status
Deferred
Published
Oct 8, 2026, 6:16 AM
Modified
Oct 8, 2026, 8:51 PM