Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-49065 – Unauthenticated Broken Access Control – Hippoo Mobile App for WooCommerce (WordP…

Be the first to know when new zero-days emerge:

Summary

CVE-2026-49065 is a high-severity Unauthenticated Broken Access Control vulnerability (CWE-862: Missing Authorization) affecting the Hippoo Mobile App for WooCommerce WordPress plugin in versions up to and including 1.9.5. The flaw allows any unauthenticated remote attacker to invoke privileged plugin actions without valid credentials, yielding a CVSS v3.1 base score of 8.2 (High). WooCommerce store operators running an affected version of this plugin are advised to upgrade to version 1.9.6 immediately.

Technical details

  • Root cause: A missing authorization, authentication, or nonce token check within a plugin function permits an unprivileged user to execute an action that should be restricted to authenticated, higher-privileged roles (CWE-862: Missing Authorization).
  • Trigger conditions: No authentication, no user interaction, and no special network position are required — the vulnerability is fully exploitable by any remote party with HTTP access to the target WordPress site.
  • Attack vector: Network-based (AV:N), low complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N).
  • Impact: High confidentiality impact (C:H) and low integrity impact (I:L), with no availability impact (A:N) — attackers can access or expose sensitive store data and perform limited unauthorized write operations. – Context: Hippoo is a server-side WordPress plugin that exposes REST API endpoints (e.g., under /wp-json/hippoo/v1/) to integrate WooCommerce stores with the Hippoo mobile app (Android and iOS). The broken access control resides within these server-side REST endpoints, making the vulnerability directly reachable over the internet. This CVE follows a patch introduced in version 1.9.5 that addressed a separate critical privilege-escalation flaw (CVE-2026-49060, CVSS 9.8), indicating an ongoing pattern of access control weaknesses in the plugin.

Affected software

  • Hippoo Mobile App for WooCommerce (WordPress plugin by hippooo): all versions <= 1.9.5

Severity

  • CVSS v3.1 Base Score: 8.2 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Mitigation and recommended actions

  • Immediate action — apply the patch: Upgrade the Hippoo Mobile App for WooCommerce plugin to version 1.9.6 or later. The plugin changelog confirms 1.9.6 as a "Critical security bug fix" release. The patched version is available directly from the WordPress Plugin Directory.
  • If immediate patching is not possible: Restrict external access to WordPress REST API endpoints served by the Hippoo plugin (e.g., paths matching /wp-json/hippoo/) at the web server or WAF level until the update can be applied.
  • General hygiene: Audit all active WordPress plugins for outdated versions, and ensure WooCommerce REST API access is restricted to authenticated, authorized consumers only.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge