CVE-2024-32111 MEDIUM

CVE-2024-32111: WordPress core < 6.5.5 - Auth. Arbitrary .html File Read (Windows Only) vulnerability

Vendor Automattic
Product WordPress
Weakness CWE-22 · Path traversal
Published June 25, 2024
Last update April 28, 2026

CVSS base score

5.0/10
Attack vector Network
Attack complexity High
Privileges required Low
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

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

What the vulnerability does

01Description

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Automattic WordPress allows Relative Path Traversal.This issue affects WordPress: from 6.5 through 6.5.4, from 6.4 through 6.4.4, from 6.3 through 6.3.4, from 6.2 through 6.2.5, from 6.1 through 6.1.6, from 6.0 through 6.0.8, from 5.9 through 5.9.9, from 5.8 through 5.8.9, from 5.7 through 5.7.11, from 5.6 through 5.6.13, from 5.5 through 5.5.14, from 5.4 through 5.4.15, from 5.3 through 5.3.17, from 5.2 through 5.2.20, from 5.1 through 5.1.18, from 5.0 through 5.0.21, from 4.9 through 4.9.25, from 4.8 through 4.8.24, from 4.7 through 4.7.28, from 4.6 through 4.6.28, from 4.5 through 4.5.31, from 4.4 through 4.4.32, from 4.3 through 4.3.33, from 4.2 through 4.2.37, from 4.1 through 4.1.40.

Explanation of Vulnerability in Simple Terms

02Summary

WordPress 6.5 through 6.5.4 contains a path traversal vulnerability in core functionality. An authenticated attacker with low privileges can read, modify, or delete files outside the intended directory by manipulating file paths. The vulnerability requires high attack complexity and does not require user interaction. Update to a version newer than 6.5.4.

What an attacker can do

03Attacker Capabilities

Read, modify, or delete files on the site outside the intended directory.

Potential impact on your site

04Site Impact

Sensitive files could be exposed, modified, or deleted; site integrity and confidentiality at risk.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege WordPress account; high attack complexity suggests specific conditions must be met.

Key dates

06Disclosure timeline

June 25, 2024 CVE published
April 28, 2026 Record updated

Related vulnerabilities

08Related CVE