Skip to main content
VulnerabilityPublished Updated

CVE-2026-111601: Hippoo Mobile App for WooCommerce (WordPress plugin) · Cross-site Scripting

Affects Hippoo Mobile App for WooCommerce (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
hippoooHippoo Mobile App for WooCommerceAffected
  • <=1.12.0
Fixed in–

AI-suggested

Users should monitor the vendor's advisory channels for updates. In the meantime, avoid clicking on suspicious links involving the 'token_id' parameter in affected versions. Implementing web application firewall (WAF) rules to detect and block malicious payloads targeting this parameter may provide temporary mitigation.

Description

The Hippoo Mobile App for WooCommerce WordPress plugin is vulnerable to reflected cross-site scripting (XSS) via the 'token_id' parameter in all versions up to and including 1.12.0. This vulnerability arises from insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject arbitrary scripts that execute when a user interacts with a crafted link. The vulnerability bypasses URL path regex constraints due to query-string parameter precedence in WP_REST_Request.

References

Community reviews

Loading reviews…