CVE-2023-6113: The WP STAGING WordPress Backup Plugin before 3.1.3 and WP STAGING Pro WordPress Backup Plugin before 5.1.3 do

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

wp staging: upgrade to 3.1.3. Exact commands for each OS are on this page.

Q: Is CVE-2023-6113 being exploited?

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

CVE-2023-6113 affects wp staging. Severity is high (CVSS 7.5). The WP STAGING WordPress Backup Plugin before 3.1.3 and WP STAGING Pro WordPress Backup Plugin before 5.1.3 do not prevent visitors from leaking key information about ongoing backups processes, allowing unauthenticated attackers to download

Q: How urgent is CVE-2023-6113?

Priority 50/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.5REMOTEUPGRADE

CVE-2023-6113 is a high-severity flaw (CVSS 7.5) affecting wp staging. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The WP STAGING WordPress Backup Plugin before 3.1.3 and WP STAGING Pro WordPress Backup Plugin before 5.1.3 do not prevent visitors from leaking key information about ongoing backups processes, allowing unauthenticated attackers to download said backups later.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.8% (top 44%)
CISA exploited list	No
Published	2024-01-01
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: wp-staging

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

Am I affected?

Timeline

2024-01-01 15:15 UTCPublished CVE record published
2026-06-17 06:50 UTCUpdated Record last modified

wp-staging wp staging UPGRADE

Affected: < 3.1.3

Fixed in: 3.1.3

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wp-staging || rpm -q wp-staging || wp-staging --version

2. UPGRADE to 3.1.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wp-staging

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wp-staging

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

wp staging: upgrade to 3.1.3. Exact commands for each OS are on this page.

Is CVE-2023-6113 being exploited?

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

CVE-2023-6113 affects wp staging. Severity is high (CVSS 7.5). The WP STAGING WordPress Backup Plugin before 3.1.3 and WP STAGING Pro WordPress Backup Plugin before 5.1.3 do not prevent visitors from leaking key information about ongoing backups processes, allowing unauthenticated attackers to download

How urgent is CVE-2023-6113?

Priority 50/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-5551 HIGH 7.5 UPGRADE The WP STAGING Pro WordPress Backup Plugin plugin for WordPress is vulnerable to Cross-Site Request Forgery in
CVE-2024-4469 HIGH 7.5 UPGRADE The WP STAGING WordPress Backup Plugin WordPress plugin before 3.5.0 does not prevent users with the administ
CVE-2024-2309 MEDIUM 4.8 UPGRADE The WP STAGING WordPress Backup Plugin WordPress plugin before 3.4.0, wp-staging-pro WordPress plugin before
CVE-2023-7204 HIGH 7.5 UPGRADE The WP STAGING WordPress Backup plugin before 3.2.0 allows access to cache files during the cloning process wh

References

← Back to latest CVEs