CVE-2022-1577: The Database Backup for WordPress plugin before 2.5.2 does not have CSRF check in place when updating the sche

Q: How do I fix CVE-2022-1577?

database backup: upgrade to 2.5.2. Exact commands for each OS are on this page.

Q: Is CVE-2022-1577 being exploited?

CVE-2022-1577 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-1577 affect?

CVE-2022-1577 affects database backup. Severity is medium (CVSS 5.4). 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 ca

Q: How urgent is CVE-2022-1577?

Priority 33/100. Public exploit reference

Routine

MEDIUM 5.4UPGRADE

CVE-2022-1577 is a medium-severity flaw (CVSS 5.4) affecting database backup. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	5.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.4% (top 63%)
CISA exploited list	No
Weakness	CWE-352
Published	2022-06-08
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: deliciousbrains

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-06-08 10:15 UTCPublished CVE record published
2026-06-17 04:22 UTCUpdated Record last modified

deliciousbrains database backup UPGRADE

Affected: < 2.5.2

Fixed in: 2.5.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy database-backup || rpm -q database-backup || database-backup --version

2. UPGRADE to 2.5.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade database-backup

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade database-backup

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-1577?

database backup: upgrade to 2.5.2. Exact commands for each OS are on this page.

Is CVE-2022-1577 being exploited?

CVE-2022-1577 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-1577 affect?

CVE-2022-1577 affects database backup. Severity is medium (CVSS 5.4). 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 ca

How urgent is CVE-2022-1577?

Priority 33/100. Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2022-0255 HIGH 7.2 UPGRADE The Database Backup for WordPress plugin before 2.5.1 does not properly sanitise and escape the fragment param
CVE-2021-24322 MEDIUM 5.4 UPGRADE The Database Backup for WordPress plugin before 2.4 did not escape the backup_recipient POST parameter in befo

References

← Back to latest CVEs