1-minute read of a 6 min report

Magento Zero-Day Lets Attackers Backdoor Fully Patched Online Stores

By

1-minute read

What a defender needs to know

Attackers are exploiting StyleSmuggler, an unpatched Magento chain that runs PHP without authentication while the platform renders a failed-payment email. Sansec reproduced it on versions 2.4.7 through 2.4.9; its first victim ran patched 2.4.6-p15. Adobe had not issued an advisory, CVE, official fix, or workaround when the primary records were captured.

The first request poisons a Magento log or report with PHP. A second request drives template and dependency-injection code to include that file. The implant runs as [kworker/u:8:0] under the site user, installs at ~/.local/share/.gvfsd/gvfsd-user, and persists through a cron job that invokes it every five minutes. The download host is 247[.]cdnflare[.]xyz.

Hunt beyond the Magento webroot. Check non-root bracketed processes with real memory, the site user’s crontab, ~/.local/share/.gvfsd/, /tmp/.kw_*, /tmp/.gvfsd-*, and both var/report/ and var/log/ for poisoned PHP. Preserve and hash /proc/<pid>/exe because Disrex found a running build that differed from the file on disk. Quiet outbound traffic does not clear a host; one implant read local Redis without contacting published command infrastructure.

Preserve evidence, remove persistence before stopping processes, then rotate every credential the Magento user could read and hunt for secondary access. Sansec recommends temporarily disabling GraphQL where the storefront can tolerate it. Disrex publishes an unofficial CLI-only scanner guard with explicit testing limits; query-string rules alone can be bypassed by body-carried parameters.

After containment, wait beyond one cron cycle and repeat process, cron, path, and log checks. The expected result is no suspicious site-user process, no recreated persistence or dropped file, and no new exploit-shaped request reaching PHP. A returning artifact means containment failed.

Primary sources