CVE-2023-7232

Backup and Restore WordPress WordPress <= 1.45 - Unauthenticated Information Exposure via Log Files

2024-03-05 00:00
Dmitrii Ignatyev

Strategic Overview

Status
Patched in 1.50
Affected Plugin
WP BackItUp Community Edition
Affected Version
<= 1.45
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2023-7232
View all WP BackItUp Community Edition vulnerabilities

At a glance

CVE-2023-7232 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WP BackItUp Community Edition WordPress plugin, affecting versions <= 1.45. 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 1.50; sites on affected versions should update now. Disclosed March 2024, reported by Dmitrii Ignatyev.

Vulnerability Overview

The Backup and Restore WordPress – Backup Plugin plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.45 via log files. This makes it possible for unauthenticated attackers to extract potentially sensitive information via log files.

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 BackItUp Community Edition <= 1.45 takes no account at all. 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 BackItUp Community Edition the fix is 1.50: builds <= 1.45 are affected, anything from 1.50 onward is not.

Remediation

Update to version 1.50, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WP BackItUp Community Edition 1.50 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-7232https://www.wordfence.com/threat-intel/vulnerabilities/id/6db51b8e-2e4b-4041-b261-d46cfdb372dchttps://nvd.nist.gov/vuln/detail/CVE-2023-7232

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C