Full server takeover risk for sites using ThemeREX Let's Play v1.1.15 via critical CVE-2026-93935
A critical vulnerability in the Let's Play plugin allows untrusted data deserialization, risking full server compromise for sites using versions up to 1.1.15.

Key points
- The flaw is CVE-2026-93935 with a CVSS score of 9.8.
- It affects ThemeREX Group Let's Play versions from n/a through 1.1.15.
- The vulnerability stems from CWE-502 deserialization of untrusted data.
Organisations running the ThemeREX Group Let's Play plugin face immediate exposure to remote object injection attacks due to a critical deserialization flaw identified as CVE-2026-93935. Security researchers have assigned the vulnerability a CVSS score of 9.8, classifying it as critical severity. This high rating reflects the ease with which attackers can exploit the weakness to inject malicious objects into the application environment.
The vulnerability exists within the plugin’s handling of untrusted data, specifically allowing the deserialization of inputs that have not been properly validated. According to the National Vulnerability Database record, this issue impacts all versions of the Let's Play plugin from its initial release through version 1.1.15. Any website utilizing these affected versions is potentially vulnerable to exploitation without additional compensating controls.
What we know
The core technical weakness behind CVE-2026-93935 is classified under CWE-502, which denotes the deserialization of untrusted data. This type of vulnerability occurs when an application deserializes untrusted data without sufficiently verifying that the resulting data is valid. Attackers can craft malicious serialized data that, when processed by the vulnerable plugin, leads to object injection.
Object injection can allow attackers to execute arbitrary code on the server hosting the application. This means that a successful exploitation of CVE-2026-93935 could result in full compromise of the underlying system. The National Vulnerability Database confirms that the vulnerability affects the ThemeREX Group Let's Play plugin specifically. No other products or vendors are mentioned in the current advisory.
The affected software range includes all iterations of the Let's Play plugin up to and including version 1.1.15. There is no indication in the source material that versions prior to the initial release are excluded, suggesting the flaw has been present since the product's inception. Security teams must verify their current installed version against this affected range to determine their risk level.
Defender's checklist
- Identify all instances of the ThemeREX Group Let's Play plugin across your infrastructure.
- Verify the installed version of the plugin on each affected system.
- Confirm if the version is 1.1.15 or earlier to determine exposure.
- Monitor network traffic for signs of abnormal deserialization attempts or object injection payloads.
What to do and how to stay safe: ThemeREX
- Audit your plugin inventory to locate any installations of the Let's Play plugin by ThemeREX Group.
- Check the version number of each installed instance to see if it falls within the affected range up to 1.1.15.
- Implement web application firewalls or intrusion prevention systems to block known object injection patterns.
- Monitor server logs for unusual deserialization errors or unexpected object creation events that may indicate exploitation attempts.
Step-by-step guide: Virtual Patching: Benefits, Limits and When to Use It
General security guidance from the TechWire Beat newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is the CVSS score for the Let's Play plugin vulnerability?
The National Vulnerability Database assigns CVE-2026-93935 a CVSS score of 9.8, which is rated as critical severity.
Which versions of the Let's Play plugin are affected by this flaw?
The vulnerability affects all versions of the ThemeREX Group Let's Play plugin from its initial release (n/a) through version 1.1.15.
Is there a patch available for CVE-2026-93935?
The source material does not confirm the availability of a patch or update for this vulnerability yet.



