Stored script execution via insufficient sanitization
Published Dec 24, 2025 · Updated Dec 24, 2025
Stored cross-site scripting in Live Composer Page Builder 2.0.5 and earlier allows remote authenticated users to inject web scripts. Published records do not identify the affected field or function; they state only that input is insufficiently sanitized and output insufficiently escaped. Contributor-level access is required, and the stored payload executes when another user opens the affected page, exposing that user's browser session to script-driven actions.
Summary
What happened
Stored cross-site scripting in Live Composer Page Builder 2.0.5 and earlier allows remote authenticated users to inject web scripts. Published records do not identify the affected field or function; they state only that input is insufficiently sanitized and output insufficiently escaped. Contributor-level access is required, and the stored payload executes when another user opens the affected page, exposing that user's browser session to script-driven actions.
The record
- CVE
- CVE-2025-68598
- Published
- Dec 24, 2025
- Updated
- Dec 24, 2025
- Vendor
- Live Composer
- Product
- Live Composer Page Builder
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 24, 2025CVE publishedPublication date reported by the CVE source.
- Dec 24, 2025Record 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 <=<= 2.0.5
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