CVE-2026-114570 — WordPress Core <= 7.0.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via Quick Edit
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Wordpress WordPress).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (cross-site scripting), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Wordpress | WordPress |
≥ 5.9.0 and ≤ 5.9.13≥ 7.0.0 and ≤ 7.0.2≥ 6.9.0 and ≤ 6.9.5≥ 6.8.0 and ≤ 6.8.6≥ 6.7.0 and ≤ 6.7.5≥ 6.6.0 and ≤ 6.6.5≥ 6.5.0 and ≤ 6.5.8≥ 6.4.0 and ≤ 6.4.8 and 16 more≥ 6.3.0 and ≤ 6.3.8≥ 6.2.0 and ≤ 6.2.9≥ 6.1.0 and ≤ 6.1.10≥ 6.0.0 and ≤ 6.0.12≥ 4.7.0 and ≤ 4.7.33≥ 5.8.0 and ≤ 5.8.13≥ 5.7.0 and ≤ 5.7.15≥ 5.6.0 and ≤ 5.6.17≥ 5.5.0 and ≤ 5.5.18≥ 5.4.0 and ≤ 5.4.19≥ 5.3.0 and ≤ 5.3.21≥ 5.2.0 and ≤ 5.2.24≥ 5.1.0 and ≤ 5.1.22≥ 5.0.0 and ≤ 5.0.25≥ 4.9.0 and ≤ 4.9.29≥ 4.8.0 and ≤ 4.8.28 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 4.9 | CVSS 3.1 | Medium | 1.8 | 2.7 | security@wordfence.com via NIST National Vulnerability Database |
| 4.9 | CVSS 3.1 | Medium | — | — | Wordfence via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N (score shown at the top: security@wordfence.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 22, 2026 → Oct 30, 2026 · 9 reading(s) · max 0.23%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Monitor CSP violation reports and script payloads in reflected parameters.
Timeline
What happened to this CVE, newest first.
- 2026
- SSVC assessment updated
- Source status changed · Received → Deferred
- Affected products added · wordpress foundation/wordpress
- Record published
- CVSS changed · 4.9
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 22, 2026 – Oct 22, 2026
- 1× Official description updated · Oct 22, 2026 – Oct 22, 2026
References
3 on the record
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-119977 WordPress Core 4.7.0 - 7.1.3 - Unauthenticated Upgrade-Window Staged-Installer Remote Code Execution 15h
- High CVE-2026-87902 WordPress Core Remote File Inclusion Vulnerability KEV Sep 22, 2026
- High CVE-2026-65640 Unrestricted Upload of File with Dangerous Type in WordPress Aug 17, 2026
- High CVE-2026-64638 Cross-site Scripting (XSS) in WordPress Aug 7, 2026
- Critical CVE-2026-63030 WordPress Core Interpretation Conflict Vulnerability KEV Jul 17, 2026
- Medium CVE-2026-60137 WordPress Core SQL Injection Vulnerability KEV Jul 17, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-114570 is "WordPress Core <= 7.0.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via Quick Edit", rated Medium. It affects WordPress (Wordpress); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.9 describes technical severity. EPSS 0.23% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.