Stored XSS via unescaped author display name
Published May 16, 2024 · Updated Apr 8, 2026
Stored XSS in Yoast SEO 22.6 and earlier allows remote authenticated users to execute arbitrary scripts through crafted author display names. The Enhanced Slack Sharing presenter writes the post author's display_name into twitter:data meta content without HTML attribute escaping. Contributor-level access is sufficient to store the payload, which executes in the browser of anyone who visits an affected post.
Summary
What happened
Stored XSS in Yoast SEO 22.6 and earlier allows remote authenticated users to execute arbitrary scripts through crafted author display names. The Enhanced Slack Sharing presenter writes the post author's display_name into twitter:data meta content without HTML attribute escaping. Contributor-level access is sufficient to store the payload, which executes in the browser of anyone who visits an affected post.
The record
- CVE
- CVE-2024-4984
- Published
- May 16, 2024
- Updated
- Apr 8, 2026
- Vendor
- Yoast
- Product
- Yoast SEO
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 16, 2024CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=22.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo