Reflected XSS via unescaped stage parameter
Published Aug 30, 2023 · Updated Apr 28, 2026
Reflected XSS in Teplitsa of Social Technologies Leyka 3.30.1 and earlier lets remote attackers inject scripts via the stage parameter. The request handler reflects stage input into generated HTML without sufficient sanitization or output escaping, causing a browser to interpret attacker-controlled markup. Exploitation requires a victim to follow a crafted link, after which the script runs in the security context of the affected WordPress site.
Summary
What happened
Reflected XSS in Teplitsa of Social Technologies Leyka 3.30.1 and earlier lets remote attackers inject scripts via the stage parameter. The request handler reflects stage input into generated HTML without sufficient sanitization or output escaping, causing a browser to interpret attacker-controlled markup. Exploitation requires a victim to follow a crafted link, after which the script runs in the security context of the affected WordPress site.
The record
- CVE
- CVE-2023-33325
- Published
- Aug 30, 2023
- Updated
- Apr 28, 2026
- Vendor
- Teplitsa of Social Technologies
- Product
- Leyka
- Classifications
- CWE-79, CAPEC-591, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 30, 2023CVE 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 <=3.30.1 changes=[{"at":"3.30.2","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