Loading vulnerability…
CVE-2026-49060 is an incorrect privilege assignment vulnerability in the Hippoo Mobile App for WooCommerce WordPress plugin through version 1.9.4. The flaw permits remote privilege escalation. The available information does not identify the affected function, endpoint, or authorization check responsible for the improper privilege assignment.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a self-contained local Docker lab and Python PoC for CVE-2026-49060, an incorrect privilege assignment / privilege escalation issue in the WordPress plugin Hippoo Mobile App for WooCommerce. The repo contains 6 files: a large README documenting the vulnerability and lab workflow, a docker-compose stack that provisions vulnerable and patched WordPress environments, two Dockerfiles that build WordPress images with Hippoo 1.9.4 and 1.9.5 respectively, and the main exploit/validator script at poc/poc.py. The exploit capability is straightforward: the Python script probes Hippoo's cloned REST namespace and targets the cloned users endpoint /wc-hippoo/v1/ext/wp/v2/users/{user_id}. On vulnerable Hippoo 1.9.4, the script can perform unauthenticated GET requests to confirm access and unauthenticated POST requests to update the selected user's password, effectively enabling account takeover of the WordPress user (default user ID 1, typically admin in this lab). On the patched 1.9.5 target, the same request path is expected to return 403 Forbidden. The script is intentionally constrained to localhost, 127.0.0.1, and ::1, making it a local-lab exploit rather than a general internet-targeting tool. Repository structure and purpose: - README.md: documents the vulnerability, affected/patched versions, expected behavior, local-only scope, and usage examples. - docker-compose.yml: orchestrates MariaDB, vulnerable WordPress, patched WordPress, and initialization containers that install/configure WordPress, WooCommerce, and Hippoo. - vuln/Dockerfile: builds the vulnerable WordPress image with Hippoo 1.9.4. - patched/Dockerfile: builds the patched comparison image with Hippoo 1.9.5. - poc/poc.py: main exploit/validator script using urllib to discover REST availability, probe the cloned route, and optionally submit a password update. This is a real exploit PoC rather than just a detector because it includes an active password-changing action. However, it is not weaponized: there is no persistence, shell, malware, callback, or framework integration. The overall maturity is best classified as OPERATIONAL.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.