Stored script execution in viewer browsers
Published Feb 1, 2024 · Updated Apr 28, 2026
Stored XSS in Page Builder: Live Composer 1.5.23 and earlier allows remote authenticated users to execute script in a viewer's browser. Patchstack has not published the affected input, handler, or missing output-encoding operation, so the concrete injection locus is undisclosed. Exploitation requires low-privileged WordPress access and a separate user to view the stored content, limiting execution to that viewer's browser context.
Summary
What happened
Stored XSS in Page Builder: Live Composer 1.5.23 and earlier allows remote authenticated users to execute script in a viewer's browser. Patchstack has not published the affected input, handler, or missing output-encoding operation, so the concrete injection locus is undisclosed. Exploitation requires low-privileged WordPress access and a separate user to view the stored content, limiting execution to that viewer's browser context.
The record
- CVE
- CVE-2023-52193
- Published
- Feb 1, 2024
- Updated
- Apr 28, 2026
- Vendor
- Live Composer Team
- Product
- Page Builder: Live Composer
- Classifications
- CWE-79, CAPEC-592
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 1, 2024CVE publishedPublication date reported by the CVE source.
- Apr 28, 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=n/a <=1.5.23 changes=[{"at":"1.5.24","status":"unaffected"}]
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