SECURITYCRITICALCVE-2026-4357

CVE-2026-4357: Maximum-Severity File Upload Flaw in Embed HTML5 Game Plugin

A perfect-10 CVSS unauthenticated file upload bug in the Embed HTML5 Game WordPress plugin lets attackers drop PHP backdoors with zero access.

Dylan H.

Security Team

September 3, 2026
4 min read
CVE-2026-4357: Maximum-Severity File Upload Flaw in Embed HTML5 Game Plugin

Critical severity

Rated critical. Prioritise patching — see the remediation guidance below.

Affected Products

  • Embed HTML5 Game WordPress Plugin ≤ 1.3

Executive Summary

CVE-2026-4357 affects the Embed HTML5 Game WordPress plugin (versions through 1.3) and carries a maximum CVSS score of 10.0 — the ceiling of the scale. The plugin fails to restrict who can upload files through it and fails to validate what gets uploaded, letting unauthenticated attackers plant PHP backdoors on any site running it.

CVSS Score: 10.0 (Critical)

There is no login wall, no capability check, and no file-type filtering standing between a remote attacker and a working web shell.


Vulnerability Overview

AttributeValue
CVE IDCVE-2026-4357
CWECWE-434 (Unrestricted Upload of File with Dangerous Type)
CVSS Score10.0 (Critical)
VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Attack VectorNetwork (no authentication required)
Privileges RequiredNone
User InteractionNone
AssignerWPScan

Affected Versions

PluginAffected VersionsFixed Version
Embed HTML5 Game≤ 1.3None published at time of writing

No patched release has been published for this plugin as of disclosure. Sites should treat it as permanently vulnerable until the vendor ships a fix.


Attack Vector

1. Attacker identifies a WordPress site running Embed HTML5 Game
2. Attacker sends an unauthenticated upload request to the plugin's upload handler
3. The plugin accepts the file with no access control or extension check
4. A PHP backdoor is written to a web-accessible directory
5. Attacker requests the backdoor directly over HTTP
6. Full remote code execution and site compromise

Impact of Successful Exploitation

ImpactDescription
Remote Code ExecutionArbitrary PHP execution on the server
Full Site TakeoverAdmin account creation, content tampering
Database CompromiseRead/write via wp-config.php credentials
Web Shell PersistenceBackdoors survive routine updates
Malware / Spam InjectionServing malicious content to site visitors

Immediate Remediation

Step 1: Deactivate and Remove the Plugin

# Via WP-CLI
wp plugin deactivate embed-html5-game
wp plugin delete embed-html5-game

Or through WordPress admin: Plugins > Installed Plugins > Embed HTML5 Game > Deactivate > Delete.

Step 2: Scan for Existing Compromise

# Search for recently created/modified PHP files
find /path/to/wordpress/wp-content/ -name "*.php" -newer /path/to/wordpress/wp-includes/version.php -type f
 
# Check for common web shell signatures
grep -rl "eval\s*(base64_decode" /path/to/wordpress/wp-content/
grep -rl "system\s*(\|shell_exec\s*(\|passthru\s*(" /path/to/wordpress/wp-content/uploads/
 
# Verify WordPress core integrity
wp core verify-checksums

If Immediate Removal Isn't Possible

  1. Block the plugin's upload endpoint at the web server or WAF level
  2. Restrict PHP execution in wp-content/uploads/ via server config (.htaccess / nginx location block)
  3. Monitor access logs for unauthenticated POST requests to the plugin's paths

Detection Indicators

IndicatorDescription
Unauthenticated POST requests to the plugin's upload pathExploitation attempts
New PHP files in uploads directoriesBackdoors dropped through the flaw
Requests to newly created .php filesAttacker accessing an uploaded backdoor
Unexpected outbound connections from the web serverPost-exploitation activity

Post-Remediation Steps

  1. Confirm the plugin is fully removed
  2. Scan for web shells and unauthorized file changes
  3. Review all admin accounts for unauthorized additions
  4. Rotate all credentials — WordPress admin, database, API keys
  5. Regenerate WordPress security keys with wp config shuffle-salts
  6. Deploy a WAF (Wordfence, Sucuri) for ongoing protection
  7. Disable PHP execution in the uploads directory as a standing hardening measure

References