CVE-2022-4931: The BackupWordPress plugin for WordPress is vulnerable to information disclosure in versions up to, and includ

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

backupwordpress: upgrade to newer than 3.12. Exact commands for each OS are on this page.

Q: Is CVE-2022-4931 being exploited?

CVE-2022-4931 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-4931 affect?

CVE-2022-4931 affects backupwordpress. Severity is medium (CVSS 4.3). The BackupWordPress plugin for WordPress is vulnerable to information disclosure in versions up to, and including 3.12. This is due to missing authorization on the heartbeat_received() function that triggers on WordPress heartbeat. This mak

Q: How urgent is CVE-2022-4931?

Priority 25/100. No elevated risk signals yet.

Routine

MEDIUM 4.3UPGRADE

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

The BackupWordPress plugin for WordPress is vulnerable to information disclosure in versions up to, and including 3.12. This is due to missing authorization on the heartbeat_received() function that triggers on WordPress heartbeat. This makes it possible for authenticated attackers, with subscriber-level permissions and above to retrieve back-up paths that can subsequently be used to download the back-up.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.5% (top 60%)
CISA exploited list	No
Published	2023-03-07
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: xibodevelopment

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

Am I affected?

Timeline

2023-03-07 15:15 UTCPublished CVE record published
2026-06-17 05:22 UTCUpdated Record last modified

xibodevelopment backupwordpress UPGRADE

Affected: <= 3.12

Fixed in: newer than 3.12

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy backupwordpress || rpm -q backupwordpress || backupwordpress --version

2. UPGRADE to newer than 3.12 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade backupwordpress

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade backupwordpress

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-4931?

backupwordpress: upgrade to newer than 3.12. Exact commands for each OS are on this page.

Is CVE-2022-4931 being exploited?

CVE-2022-4931 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-4931 affect?

CVE-2022-4931 affects backupwordpress. Severity is medium (CVSS 4.3). The BackupWordPress plugin for WordPress is vulnerable to information disclosure in versions up to, and including 3.12. This is due to missing authorization on the heartbeat_received() function that triggers on WordPress heartbeat. This mak

How urgent is CVE-2022-4931?

Priority 25/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs