CVE-2026-4357

10.0

WordPress · Embed HTML5 Game

The Embed HTML5 Game WordPress plugin allows unauthenticated attackers to upload arbitrary files, leading to potential remote code execution via PHP backdoors.

Executive summary

A critical unauthenticated file upload vulnerability in the Embed HTML5 Game WordPress plugin allows attackers to execute arbitrary code, posing a severe risk of total system compromise.

Vulnerability

This vulnerability is an unrestricted upload of a file with a dangerous type (CWE-434), where the plugin fails to perform necessary authentication or file type validation, allowing unauthenticated attackers to upload malicious scripts directly to the server.

Business impact

The ability for an unauthenticated attacker to upload and execute arbitrary PHP code results in a full compromise of the web server. This level of access grants the attacker the power to exfiltrate sensitive data, modify website content, or use the server as a pivot point for further attacks on the internal network, justifying its critical CVSS score of 10.0.

Remediation

Immediate Action: Since no specific patch version is currently identified, administrators should immediately deactivate and remove the Embed HTML5 Game plugin from all WordPress installations until a secure version is released by the vendor.

Proactive Monitoring: Review web server access logs for unusual POST requests targeting plugin directories and monitor for the creation of new, unexpected files in the upload folders.

Compensating Controls: Deploy a Web Application Firewall (WAF) configured to block unauthorized file uploads and restrict access to common plugin upload endpoints to known administrative IP addresses.

Exploitation status

Public Exploit Available: Unknown.

Analyst recommendation

Given the critical nature of this vulnerability and the ease with which it can be exploited by unauthenticated actors, immediate action is required. Organizations should prioritize the removal of the vulnerable component and implement strict file upload policies to prevent further risk to the production environment.

More WordPress CVEs

Sources

Originally found and disclosed by Mike Gozdiskowski, with WPScan (coordinator), per the CVE Program record.