Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-14461: CWE-862 Missing Authorization in tpixendit Xendit Payment

0
Medium
VulnerabilityCVE-2025-14461cvecve-2025-14461cwe-862
Published: Wed Feb 04 2026 (02/04/2026, 08:25:28 UTC)
Source: CVE Database V5
Vendor/Project: tpixendit
Product: Xendit Payment

Description

The Xendit Payment plugin for WordPress is vulnerable to unauthorized order status manipulation in all versions up to, and including, 6.0.2. This is due to the plugin exposing a publicly accessible WooCommerce API callback endpoint (`wc_xendit_callback`) that processes payment callbacks without any authentication or cryptographic verification that the requests originate from Xendit's payment gateway. This makes it possible for unauthenticated attackers to mark any WooCommerce order as paid by sending a crafted POST request to the callback URL with a JSON body containing an `external_id` matching the order ID pattern and a `status` of 'PAID' or 'SETTLED', granted they can enumerate order IDs (which are sequential integers). This leads to orders being fraudulently marked as completed without any actual payment, resulting in financial loss and inventory depletion.

AI-Powered Analysis

AILast updated: 02/04/2026, 09:03:01 UTC

Technical Analysis

CVE-2025-14461 is a vulnerability classified under CWE-862 (Missing Authorization) found in the Xendit Payment plugin for WordPress, which integrates payment processing into WooCommerce stores. The vulnerability exists because the plugin exposes a publicly accessible API callback endpoint named `wc_xendit_callback` that processes payment status updates without any form of authentication or cryptographic verification to confirm that the requests originate from Xendit's legitimate payment gateway. This lack of authorization allows an attacker to send crafted POST requests containing a JSON payload with an `external_id` matching the sequential WooCommerce order IDs and a `status` field set to 'PAID' or 'SETTLED'. Since order IDs are sequential integers and can be enumerated, an attacker can systematically mark any order as paid without completing a real transaction. This manipulation undermines the integrity of the order processing system, leading to fraudulent order completion, financial loss due to uncollected payments, and inventory depletion as goods are shipped without payment. The vulnerability affects all versions of the plugin up to and including 6.0.2. The CVSS 3.1 base score is 5.3 (medium severity), reflecting the fact that the attack vector is network-based, requires no privileges or user interaction, and impacts integrity but not confidentiality or availability. No patches or fixes are currently linked, and no known exploits have been reported in the wild. The vulnerability highlights a critical design flaw in the plugin's handling of payment callbacks, emphasizing the need for proper authentication mechanisms such as HMAC signatures or token-based verification to validate callback requests.

Potential Impact

For European organizations operating WooCommerce-based e-commerce platforms using the Xendit Payment plugin, this vulnerability poses a significant risk of financial fraud and operational disruption. Attackers can manipulate order statuses to mark unpaid orders as paid, resulting in shipment of goods without receiving payment, causing direct financial losses. Additionally, inventory records become inaccurate, potentially leading to stockouts or mismanagement. This can damage customer trust and brand reputation if fraudulent orders are fulfilled or if legitimate customers face stock shortages. The integrity of the order management system is compromised, which may also affect accounting and reconciliation processes. While the vulnerability does not expose sensitive customer data or disrupt service availability, the financial and operational impacts are substantial. European merchants in countries with high WooCommerce adoption and significant e-commerce activity are particularly vulnerable. The lack of authentication on the callback endpoint also increases the risk of automated or large-scale exploitation attempts, which could amplify losses.

Mitigation Recommendations

To mitigate this vulnerability, affected organizations should immediately implement strict authentication and verification mechanisms on the WooCommerce API callback endpoint. This includes: 1) Enforcing cryptographic verification such as HMAC signatures on callback requests to ensure they originate from the legitimate Xendit payment gateway. 2) Implementing IP whitelisting to restrict callback requests to known Xendit gateway IP addresses. 3) Adding nonce or timestamp validation to prevent replay attacks. 4) Monitoring order status changes for unusual patterns, such as rapid or bulk status updates, and setting alerts for suspicious activity. 5) Limiting the exposure of the callback endpoint by restricting access via web server configuration or firewall rules. 6) Regularly updating the plugin once a vendor patch is released to address this vulnerability. 7) Conducting security audits and penetration testing focused on payment processing workflows. 8) Educating staff to recognize and respond to potential fraud indicators. These measures go beyond generic advice by focusing on securing the callback mechanism and detecting exploitation attempts.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-10T15:58:16.899Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69830729f9fa50a62f79eb57

Added to database: 2/4/2026, 8:45:29 AM

Last enriched: 2/4/2026, 9:03:01 AM

Last updated: 2/7/2026, 1:51:44 PM

Views: 27

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats