CVE-2023-5775: The BackWPup plugin for WordPress is vulnerable to Plaintext Storage of Backup Destination Password in all ver

Q: How do I fix CVE-2023-5775?

backwpup: upgrade to 4.0.3. Exact commands for each OS are on this page.

Q: Is CVE-2023-5775 being exploited?

CVE-2023-5775 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-2023-5775 affect?

CVE-2023-5775 affects backwpup. Severity is low (CVSS 2.2). The BackWPup plugin for WordPress is vulnerable to Plaintext Storage of Backup Destination Password in all versions up to, and including, 4.0.2. This is due to to the plugin improperly storing backup destination passwords in plaintext. This

Q: How urgent is CVE-2023-5775?

Priority 17/100. No elevated risk signals yet.

Routine

LOW 2.2UPGRADE

CVE-2023-5775 is a low-severity flaw (CVSS 2.2) affecting backwpup. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The BackWPup plugin for WordPress is vulnerable to Plaintext Storage of Backup Destination Password in all versions up to, and including, 4.0.2. This is due to to the plugin improperly storing backup destination passwords in plaintext. This makes it possible for authenticated attackers, with administrator-level access, to retrieve the password from the password input field in the UI or from the options table where the password is stored.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	2.2 (Low)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	High
User interaction	None
EPSS exploit chance	0.4% (top 61%)
CISA exploited list	No
Weakness	CWE-256
Published	2024-02-26
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: inpsyde

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

Am I affected?

Timeline

2024-02-26 16:27 UTCPublished CVE record published
2026-06-17 06:49 UTCUpdated Record last modified

inpsyde backwpup UPGRADE

Affected: < 4.0.3

Fixed in: 4.0.3

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 4.0.3 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade backwpup

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-2023-5775?

backwpup: upgrade to 4.0.3. Exact commands for each OS are on this page.

Is CVE-2023-5775 being exploited?

CVE-2023-5775 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-2023-5775 affect?

CVE-2023-5775 affects backwpup. Severity is low (CVSS 2.2). The BackWPup plugin for WordPress is vulnerable to Plaintext Storage of Backup Destination Password in all versions up to, and including, 4.0.2. This is due to to the plugin improperly storing backup destination passwords in plaintext. This

How urgent is CVE-2023-5775?

Priority 17/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2023-7164 HIGH 7.5 UPGRADE The BackWPup WordPress plugin before 4.0.4 does not prevent Directory Listing in its temporary backup folder,
CVE-2023-5505 MEDIUM 6.8 UPGRADE The BackWPup plugin for WordPress is vulnerable to Directory Traversal in versions up to, and including, 4.0.1
CVE-2023-5504 HIGH 8.7 UPGRADE The BackWPup plugin for WordPress is vulnerable to Directory Traversal in versions up to, and including, 4.0.1

References

← Back to latest CVEs