High update_hijack_shape
Social Share Icons & Social Share Buttons (10k+ installs)
Suspicious
6mo ago
| Slug | ultimate-social-media-plus |
|---|---|
| Shape | plugin_upgrader_install_from_s3 |
| Vendor | Inisev (committers: iclyde, shihabsoft) |
| Wp org author | inisev |
| Active installs | 10,000 |
| Remote url | https://shopify-js-bucket.s3.ap-south-1.amazonaws.com/sfsi_worker_premium_installer-0.0.1.zip |
| File | libs/controllers/sfsi_buttons_controller.php |
| Line | 1,706 |
| Ajax endpoint | wp_ajax_worker_plugin |
| Introduced in | 3.5.4 by socialsharepro 2022-09-20 r2787689 |
| Discovered by | wp beacon hunt-updaters (direct_upgrader_install/vendor_unknown) |
| Audit rationale | Plugin admin-AJAX endpoint installs sibling plugin from Inisev-controlled AWS S3 bucket using Plugin_Upgrader::install(). No signature verification, no domain-name validation, hardcoded URL. Single S3 PUT by anyone with bucket IAM access replaces the zip and grants RCE on every site that triggers the install path. Same architectural class as historical js-support-ticket case (Audit #23) but install-via-S3 instead of eval-via-curl. S3 zip is currently 404 but bucket is alive. |
View raw JSON
{
"slug": "ultimate-social-media-plus",
"shape": "plugin_upgrader_install_from_s3",
"vendor": "Inisev (committers: iclyde, shihabsoft)",
"wp_org_author": "inisev",
"active_installs": 10000,
"remote_url": "https://shopify-js-bucket.s3.ap-south-1.amazonaws.com/sfsi_worker_premium_installer-0.0.1.zip",
"file": "libs/controllers/sfsi_buttons_controller.php",
"line": 1706,
"ajax_endpoint": "wp_ajax_worker_plugin",
"introduced_in": "3.5.4 by socialsharepro 2022-09-20 r2787689",
"discovered_by": "wp beacon hunt-updaters (direct_upgrader_install/vendor_unknown)",
"audit_rationale": "Plugin admin-AJAX endpoint installs sibling plugin from Inisev-controlled AWS S3 bucket using Plugin_Upgrader::install(). No signature verification, no domain-name validation, hardcoded URL. Single S3 PUT by anyone with bucket IAM access replaces the zip and grants RCE on every site that triggers the install path. Same architectural class as historical js-support-ticket case (Audit #23) but install-via-S3 instead of eval-via-curl. S3 zip is currently 404 but bucket is alive."
}