CVE-2023-7204

WP STAGING WordPress Backup Plugin < 3.2.0 - Sensitive Information Exposure via cache files

2024-01-31 00:00

Strategic Overview

Status: Patched in 3.2.0
Affected Plugin: WP STAGING – Backups & Restore, Migration & Clone Plugin – Cloud Backups, Scheduled Backups
Affected Version: < 3.2.0
CVSS: 5.3Medium
Weakness type: CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE: CVE-2023-7204

View all WP STAGING – Backups & Restore, Migration & Clone Plugin – Cloud Backups, Scheduled Backups vulnerabilities

At a glance

CVE-2023-7204 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WP STAGING WordPress plugin, affecting versions < 3.2.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.2.0; sites on affected versions should update now. Disclosed January 2024, reported by Dmitrii Ignatyev.

Vulnerability Overview

The WP STAGING WordPress Backup Plugin – Migration Backup Restore plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions before 3.2.0 via the cache files. This makes it possible for unauthenticated attackers to extract sensitive data.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in WP STAGING < 3.2.0 takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For WP STAGING the fix is 3.2.0: builds < 3.2.0 are affected, anything from 3.2.0 onward is not.

Remediation

Update to version 3.2.0, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: WP STAGING 3.2.0 closes this, and updating the plugin is the step that ends it.

Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-7204 https://www.wordfence.com/threat-intel/vulnerabilities/id/fe8816d8-1687-4a3c-9f2a-23f21d679cc5 https://nvd.nist.gov/vuln/detail/CVE-2023-7204

Related records

Same weakness class

Other vulnerabilities in WP STAGING – Backups & Restore, Migration & Clone Plugin – Cloud Backups, Scheduled Backups

CVSS Vector

5.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityLow
IntegrityNone
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/