# CVE-2026-86827: BackWPup 3.3 - 5.7.6 - Unauthenticated Backup Job Execution via wp-cron.php

> Unauthenticated attackers can force immediate execution of backup jobs, potentially causing resource exhaustion or exposing sensitive data.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-pcfw-vf4c-h2h5

## What is CVE-2026-86827?

CVE-2026-86827 is a medium-severity missing authorization vulnerability in Unknown BackWPup, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-86827?


## How do I fix CVE-2026-86827?

No fix has been published for CVE-2026-86827 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-86827 being exploited?

There is no known exploitation of CVE-2026-86827 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-86827 and fix it if it is affected.

What it is: CVE-2026-86827 is a medium-severity missing authorization vulnerability in Unknown BackWPup, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86827 in the wild and no public exploit code.

Affected product: Unknown BackWPup. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-86827/ (Markdown: https://insights.sbomify.com/CVE-2026-86827/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-86827
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-86827
- OSV: https://osv.dev/vulnerability/CVE-2026-86827

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-86827/
Summaries are generated and may contain mistakes; the official description above is the record.