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

New CVE Detected

CVE-2026-66473 – Authorization Bypass – Xendit Payment WordPress Plugin <= 7.1.0

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

Summary

CVE-2026-66473 is a high-severity Broken Access Control vulnerability (CWE-862: Missing Authorization) affecting the Xendit Payment WooCommerce plugin (woo-xendit-virtual-accounts) for WordPress in all versions up to and including 7.1.0. The flaw allows unauthenticated remote attackers to invoke privileged plugin functionality without any credentials or user interaction, carrying a CVSS v3.1 base score of 7.5 (High). As of the publication date (July 27, 2026), no patched version has been released.

Technical details

  • Root cause: Missing authorization, authentication, and nonce token validation on a plugin function, enabling unprivileged callers to execute actions restricted to higher privilege levels (CWE-862: Missing Authorization).
  • Trigger conditions: The vulnerability can be triggered over the network with low attack complexity; no authentication, existing account, or user interaction is required.
  • Attack vector: Network (AV:N/AC:L/PR:N/UI:N) — the affected endpoint or function is reachable directly via HTTP/HTTPS requests to the WooCommerce storefront.
  • Impact: High integrity impact (I:H) with no confidentiality or availability component. In the context of a payment gateway plugin, a missing-authorization flaw of this type enables unauthorized manipulation of payment-related functionality — such as altering order or payment status — without completing a legitimate transaction. A closely related prior vulnerability (CVE-2025-14461, affecting versions ≤ 6.0.2) documented that the same class of missing-authorization flaw in this plugin allowed unauthenticated actors to mark orders as paid via an unprotected callback endpoint, resulting in financial loss and inventory depletion for merchants.

Affected software

  • Xendit Payment WordPress/WooCommerce plugin (woo-xendit-virtual-accounts), all versions <= 7.1.0

Severity

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

Mitigation and recommended actions

  • Immediate: No official patched version is available as of July 27, 2026. Version 7.1.0 is the current latest release. Monitor the WordPress.org plugin page (woo-xendit-virtual-accounts) and apply the vendor patch as soon as it is released.
  • Interim workarounds:
    • If the plugin is not actively required, consider temporarily deactivating it until a patched version is published.
    • Apply web application firewall (WAF) rules to block unauthorized requests to the plugin’s callback and payment-processing endpoints.
    • Review WooCommerce order logs for anomalous order status transitions (e.g., orders marked as paid without a corresponding Xendit payment record) as an indicator of exploitation attempts.
    • Restrict access to WordPress admin and WooCommerce endpoints at the network or hosting level where feasible.

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