Stored XSS via insufficient output escaping
Published Jun 15, 2026 · Updated Jun 15, 2026
Stored cross-site scripting in LJ Apps WP Google Review Slider 18.0 and earlier allows remote attackers to inject scripts into site pages. Public advisories do not identify the vulnerable parameter or code locus; they report that input is stored without sufficient sanitization and rendered without output escaping. Successful exploitation requires a user to visit an injected page, where the script executes in that visitor's browser context.
Summary
What happened
Stored cross-site scripting in LJ Apps WP Google Review Slider 18.0 and earlier allows remote attackers to inject scripts into site pages. Public advisories do not identify the vulnerable parameter or code locus; they report that input is stored without sufficient sanitization and rendered without output escaping. Successful exploitation requires a user to visit an injected page, where the script executes in that visitor's browser context.
The record
- CVE
- CVE-2026-39451
- Published
- Jun 15, 2026
- Updated
- Jun 15, 2026
- Vendor
- jgwhite33
- Product
- WP Google Review Slider
- Classifications
- CWE-79, CAPEC-592, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 15, 2026CVE publishedPublication date reported by the CVE source.
- Jun 15, 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 <=18.0 changes=[{"at":"18.1","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