Unauthenticated stored XSS via unsanitized event context
Published Nov 21, 2024 · Updated Apr 8, 2026
Stored XSS in Elementor Activity Log 2.11.1 and earlier allows remote attackers to inject scripts through recorded event parameters. Theme and plugin editor hooks store event context without adequate input sanitization, and the administrative log view outputs that context without sufficient escaping. An administrator must open a poisoned log entry for the script to execute in the site administration origin, where it can read or modify data available to that session.
Summary
What happened
Stored XSS in Elementor Activity Log 2.11.1 and earlier allows remote attackers to inject scripts through recorded event parameters. Theme and plugin editor hooks store event context without adequate input sanitization, and the administrative log view outputs that context without sufficient escaping. An administrator must open a poisoned log entry for the script to execute in the site administration origin, where it can read or modify data available to that session.
The record
- CVE
- CVE-2024-10788
- Published
- Nov 21, 2024
- Updated
- Apr 8, 2026
- Vendor
- Elementor
- Product
- Activity Log – Monitor & Record User Changes
- Classifications
- CWE-79
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 21, 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 <=2.11.1
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