Stored XSS via unescaped progressbarLayout value
Published Dec 13, 2025 · Updated Dec 13, 2025
Stored XSS in Sparkle WP Kingcabs 1.1.9 and earlier allows remote authenticated users to inject scripts through progressbarLayout. The progress-bar block renderer accepts the progressbarLayout value without sufficient input sanitization and emits it into generated page output without context-appropriate escaping. Contributor-level access is required to save the payload, which executes when visitors open an affected page and can act in their browser context.
Summary
What happened
Stored XSS in Sparkle WP Kingcabs 1.1.9 and earlier allows remote authenticated users to inject scripts through progressbarLayout. The progress-bar block renderer accepts the progressbarLayout value without sufficient input sanitization and emits it into generated page output without context-appropriate escaping. Contributor-level access is required to save the payload, which executes when visitors open an affected page and can act in their browser context.
The record
- CVE
- CVE-2025-7058
- Published
- Dec 13, 2025
- Updated
- Dec 13, 2025
- Vendor
- Sparkle Themes
- Product
- Kingcabs
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 13, 2025CVE publishedPublication date reported by the CVE source.
- Dec 13, 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=* <=1.1.9
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