Unauthorized action via cross-site request forgery
Published Nov 22, 2023 · Updated Apr 28, 2026
CSRF in Teplitsa of Social Technologies Leyka 3.29.2 and earlier allows remote attackers to trigger an unspecified action. Neither the CNA record nor its vendor-linked advisory identifies the affected endpoint, handler, or missing request-verification operation. Exploitation requires an authenticated WordPress user to submit an attacker-controlled request; the resulting state change remains undisclosed.
Summary
What happened
CSRF in Teplitsa of Social Technologies Leyka 3.29.2 and earlier allows remote attackers to trigger an unspecified action. Neither the CNA record nor its vendor-linked advisory identifies the affected endpoint, handler, or missing request-verification operation. Exploitation requires an authenticated WordPress user to submit an attacker-controlled request; the resulting state change remains undisclosed.
The record
- CVE
- CVE-2023-27442
- Published
- Nov 22, 2023
- Updated
- Apr 28, 2026
- Vendor
- Teplitsa of Social Technologies
- Product
- Leyka
- Classifications
- CWE-352, CAPEC-62
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 22, 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.29.2 changes=[{"at":"3.30","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