CVE-2026-49777: Supply Chain Backdoor in Product Slider Pro for WooCommerce
CVE-2026-49777 is a critical supply-chain backdoor vulnerability affecting the commercial Product Slider Pro for WooCommerce WordPress plugin from ShapedPlugin, LLC. The issue affects releases prior to 3.5.4, with reporting also noting that all versions through 3.5.2 were affected and that version 3.5.3 is not reliably distinguishable as safe because the vendor reportedly modified an existing release in place without issuing a new version identifier. The vulnerability is classified as CWE-1284 and is described as improper validation of a quantity-related input that enabled malicious software implantation. Available reporting indicates the compromised plugin distribution contained backdoor functionality that could be triggered remotely without authentication, leading to installation of attacker-controlled code on affected WordPress sites. The issue is best understood as a maliciously backdoored premium plugin release delivered through the vendor’s official distribution channel rather than a routine isolated coding defect.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can result in full compromise of the affected WordPress site. Reported outcomes include implantation of malicious software, remote execution of attacker payloads, persistent unauthorized access, credential and two-factor authentication data theft, arbitrary file write capability, deployment of additional backdoors or web shells, and ongoing ability to re-access and abuse the site. Because the vulnerable component runs within WordPress, compromise can expose site configuration secrets, administrator accounts, mail-related credentials, and WooCommerce-associated data, with high impact to confidentiality, integrity, and availability.
Mitigation
If you can’t patch tonight, do this now.
If immediate remediation is not possible, disable the affected plugin to prevent continued execution of backdoor functionality. Restrict administrative access, plugin installation and update privileges, and external exposure of the WordPress administration interface where operationally feasible. Treat any site currently running or previously exposed to a compromised build as potentially compromised and perform forensic review for persistence, unauthorized accounts, and secondary payloads. Because version-based scanners may not reliably distinguish safe from unsafe in-place-patched builds, rely on package provenance and integrity validation rather than version string alone.
Remediation
Patch, then assume compromise.
Upgrade to a clean vendor release that definitively removes the backdoor, identified in reporting as 3.5.4 or later. Because the vendor reportedly patched an earlier release in place without changing the version number, version-only verification is unreliable for 3.5.3; installations claiming that version should not be assumed safe unless integrity has been independently validated against a trusted clean package. If a trustworthy fixed package cannot be confirmed, remove the plugin and reinstall only from a verified clean source. Given the supply-chain nature of the incident, incident response should include reviewing plugin files and database changes, removing unauthorized persistence mechanisms, rotating administrator passwords, regenerating 2FA secrets, reviewing administrator accounts, and resetting other credentials that may have been exposed, including mail and application secrets.
Exploits
3 exploits validated by Mallory's analysis. Hidden: 2 rejected by Mallory's analysis as not a working exploit.
References
Frequently asked questions
- Is CVE-2026-49777 exploited in the wild?
- Yes. As of Sep 25, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2026-49777?
- Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2026-49777, the earliest disclosed Jun 21, 2026.
- Is there a patch for CVE-2026-49777?
- Upgrade to a clean vendor release that definitively removes the backdoor, identified in reporting as 3.5.4 or later. Because the vendor reportedly patched an earlier release in place without changing the version number, version-only verification is unreliable for 3.5.3; installations claiming that version should not be assumed safe unless integrity has been independently validated against a trusted clean package.
- How severe is CVE-2026-49777?
- CVE-2026-49777 has a CVSS v3.1 score of 10.0 (Critical) and an EPSS score of 1.7% (77th percentile) as of Sep 25, 2026.
Recent activity
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.