deniz.in

Markets

Weather

Loading weather

· via dev.to (home feed)

YOOtheme Pro RCE flaw CVE-2026-102785 fixed in 5.0.53; admins urged to patch and review logs

An unauthenticated remote code execution flaw in YOOtheme Pro's image handler lets attackers plant PHP webshells on WordPress and Joomla sites; versions 5.0.0–5.0.52 are affected and 5.0.53 fixes it.

YOOtheme Pro RCE flaw CVE-2026-102785 fixed in 5.0.53; admins urged to patch and review logs

Vulnerability in the image handler

YOOtheme Pro, a commercial theme and page-builder available for both WordPress and Joomla, carries an unauthenticated remote code execution vulnerability tracked as CVE-2026-102785. According to a checklist published on dev.to, every release from 5.0.0 through 5.0.52 is affected, and YOOtheme's own changelog names 5.0.53 as the version that fixes it.

The flaw lives in the extension's image handler. An attacker takes a validly signed image URL, extends it with the parameters FromFile=php://input and a Save= operation, and writes a file that works as both a JPEG and a PHP script into a publicly reachable media directory. Because the php://input stream wrapper is accepted, the request body itself supplies the file contents.

What Unit 42 observed

Unit 42, whose threat intelligence underpins the dev.to guidance, saw automated scanners probing for the flaw, followed by hands-on activity through an ALFA Team webshell. Two details complicate detection. The server returned HTTP 500 even when the payload had been written successfully, and the implanted shell ran regardless of the error the original client received.

The indicators to hunt for follow from that behaviour. Log searches should cover requests containing yootheme=cache/, FromFile=php://input and Save=, and should include failed responses rather than excluding them. On the filesystem, the article points to PHP files named yt followed by seven hexadecimal characters, the ALFA_DATA/alfacgiapi/ directory, and a WPCONFIG response marker associated with ALFA tooling. On a Windows host, Unit 42 recorded validation via cmd.exe /s /c, an echo of a marker beginning with YTS followed by an id command, and then follow-on uploads, outbound downloads and an attempt to install gsocket.

Inventory, then patch

The dev.to checklist tells operators to start with an inventory: confirm the exact YOOtheme Pro version on every WordPress and Joomla installation, including staging copies, agency-managed marketing sites and overlooked subdomains, since a shared licence says nothing about whether each instance was updated. A ZoomEye search for pages containing "YOOtheme" in the body returned 34,682 results at the time of research, while a search referencing the CVE itself returned none — those are candidate sites rather than confirmed exposures, and verification should come from the host or a trusted management interface.

Upgrading to 5.0.53 or later is the fix, and it should reach staged copies as well as production, with a check that the active template actually reports the new version after deployment. Where patching cannot happen immediately, filtering out the malicious image-handler request patterns and stopping PHP from executing inside writable upload folders such as wp-content/uploads/ are the suggested compensating controls. The article cautions that some setups rely on PHP execution inside uploads for existing plugins, so any blocking rule should be tested against the site's real behaviour before being enforced.

Containment and recovery

Patching closes the vulnerable path but does not prove that nothing was written before the update arrived, which is why the log and filesystem review matters as much as the upgrade. If a webshell is found, the guidance is to preserve the file and its logs, isolate the host and investigate the web-server account before removing the implant. Database credentials, application secrets, administrator passwords and API keys readable from the compromised deployment should be rotated, authentication logs and connected services reviewed, and the host rebuilt or restored from a backup taken before the file write whenever integrity is in doubt. After recovery, monitoring should continue for the same request pattern.

Why it matters

This is unauthenticated code execution in a widely deployed commercial extension, so the exposure spans both WordPress and Joomla sites and requires no valid account. The evidence gathered by Unit 42 shows attackers are already automating discovery and moving to interactive access. The HTTP 500 response on successful writes means log pipelines that concentrate on successful status codes will miss real compromises, so only a deliberate search that includes error responses can confirm or rule out a breach. For anyone running YOOtheme Pro in the affected range, the update is necessary but not sufficient: the same review has to establish whether the door was opened before it was closed.

  • #security
  • #wordpress
  • #joomla
  • #vulnerability
  • #remote-code-execution

Related posts