Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2026-49777: Supply Chain Backdoor in Product Slider Pro for WooCommerce

Published Jun 5, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS10.0Critical · v3.1
EPSS1.7%77th percentile
CISA KEVNoNot listed
In the wildReported2 exploitation records in Mallory
IdentifiersCVE-2026-49777CWE-1284 · Improper Validation of Specified…

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

3 exploits validated by Mallory's analysis. Hidden: 2 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2026-49777-CVE-2026-10735Repository contains a single Python exploit script and a minimal README. The main file, CVE-2026-49777.py, is a standalone interactive exploitation tool targeting an alleged ShapedPlugin supply-chain compromise / LicenseLoader RCE affecting WordPress plugin deployments. The script is not part of a known exploitation framework. Structurally, the script includes: banner/UI code; logging helpers; result persistence to pwned.txt; IOC detection logic; login-bypass logic using a hardcoded MD5 value; RCE-related constants including a WooCommerce-style REST path (/wp-json/wc/v3/settings/apply), a command parameter key (wc_diag), and a header artifact (X-Cache-Status); single-target exploitation flow; and multithreaded bulk scanning from a user-supplied target list. The visible code shows the exploit first probing targets for compromise indicators by requesting fake plugin directories and specific PHP files under /wp-content/plugins/. It also checks the site root for an X-Cache-Status header whose 8-character alphanumeric value is treated as confirmation of header-based RCE behavior. The script then attempts a login bypass against an admin username using a hardcoded MD5 hash and proceeds toward command execution with an operator-supplied command, defaulting to id. Successful targets are recorded in pwned.txt. Overall purpose: this is an operational exploit/scanner for compromised WordPress sites, combining detection and exploitation. It supports both validation of infection/backdoor artifacts and active post-compromise command execution across one or many targets.xxconi · Disclosed Jun 21, 2026 · python · markdown · web · networkOperationalCVE-2026-49777-WooCommerce-RCESmall single-purpose exploit repository with 4 files: one Python exploit script, a README, license, and .gitignore. The main artifact is CVE-2026-49777.py, a standalone Python CLI tool using requests, argparse, and helper print/URL-normalization routines. Based on the visible code and README, it supports two phases: (1) detection/version checking of the Product Slider Pro for WooCommerce WordPress plugin and (2) active exploitation that attempts to trigger an unauthenticated remote payload download/execution path associated with CVE-2026-49777. The script includes a hardcoded vulnerable version list covering 1.0.0-1.3.1 and 2.0.0-2.2.0, supports check-only mode, optional proxying, timeout/banner options, and reports success/failure to the operator. The exploit is not part of a larger framework and appears to be an operational PoC rather than a mere detector, because it contains explicit exploitation logic intended to trigger remote code execution on the target. The README mirrors the exploit purpose in Arabic and English, documents usage, affected versions, remediation guidance, and lists post-compromise indicators such as suspicious files under the plugin cache directory and uploads directory.amnsecurity · Disclosed Jul 8, 2026 · python · markdown · web · networkOperationalCVE-2026-49777The repository contains one standalone Python 3 script, CVE-2026-49777.py, rather than a framework module. It presents itself as an exploit for alleged ShapedPlugin supply-chain compromises affecting WordPress plugins, naming CVE-2026-49777 and CVE-2026-10735. The script uses requests with TLS verification disabled and provides interactive single-target and file-based multithreaded modes. Visible logic performs HTTP probes for fake WooCommerce plugin directories and specific persistent/LicenseLoader PHP files, checks the target root response for an eight-character alphanumeric X-Cache-Status value, and defines a WooCommerce REST endpoint, a wc_diag webshell parameter, and a hardcoded MD5 value for a claimed authentication bypass. It is an active exploitation tool rather than detection-only code because its workflow accepts an OS command (default id), attempts login bypass/RCE, and records successful results in pwned.txt. No fixed victim domain or IP is embedded; all web requests are constructed from the operator-provided base URL.katranSefa · Disclosed Sep 6, 2026 · python · web · networkOperational
FAQ

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.
Activity feed

Recent activity

11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+1 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity6Community discussion across Reddit, Mastodon, and other social sources.