CVE-2025-13526: What It Is and How to Fix It

CVE-2025-13526 is a high-severity IDOR flaw in the OneClick Chat to Order WordPress plugin. By changing an order ID in a URL, anyone can view other customers' names, addresses, phone numbers and order details. Here is what is affected and how to fix it.

0 comments
On this page
  1. What is CVE-2025-13526?
  2. How does the vulnerability work?
  3. What data is exposed?
  4. How do you fix CVE-2025-13526?
  5. What should developers learn from it?
  6. Conclusion

CVE-2025-13526 is a high-severity (CVSS 7.5) Insecure Direct Object Reference vulnerability in the OneClick Chat to Order WordPress plugin, versions 1.0.8 and earlier. Unauthenticated attackers can view other customers' names, emails, phone numbers, addresses, order contents and payment methods by changing an order ID in a URL. Update to version 1.0.9 or later.

What is CVE-2025-13526?

CVE-2025-13526 is a broken access control flaw (CWE-200) in OneClick Chat to Order, a WooCommerce plugin that lets shoppers send orders via WhatsApp. Wordfence lists about 40,000 active installations.

Attribute

Detail

Plugin

OneClick Chat to Order (slug: oneclick-whatsapp-order), by walterpinem

Affected versions

All versions up to and including 1.0.8

Fixed version

1.0.9 (install the latest release; see below)

Weakness

Insecure Direct Object Reference; CWE-200 information exposure

CVSS 3.1

7.5 High (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N)

Published

22 November 2025, by Wordfence as CNA

Credited researcher

Md Shofiur Rahman

Exploitation status

CISA recorded no known exploitation (SSVC, November 2025)

How does the vulnerability work?

The plugin's wa_order_thank_you_override function loads an order from an ID supplied in the URL but never checks who is asking. It does not confirm that the visitor is logged in as the order's owner, or that a guest holds the matching order key.

Because WooCommerce order IDs are usually sequential, an attacker can open one thank-you page and simply increment the number. Each request returns another customer's order. CVSS rates this as network-reachable, low complexity, no privileges and no user interaction, with high confidentiality impact.

What data is exposed?

The advisory lists customer names, email addresses, phone numbers, billing and shipping addresses, order contents and payment methods. That is enough for targeted phishing, fraud and social engineering, and it is personal data under the GDPR. Integrity and availability are not affected.

How do you fix CVE-2025-13526?

Update the plugin, then check whether data was already harvested.

  1. Check the installed version: wp plugin get oneclick-whatsapp-order --field=version

  2. Update: wp plugin update oneclick-whatsapp-order, or update from the WordPress dashboard. Version 1.0.9 fixes this CVE, but Wordfence lists a later authorisation flaw (CVE-2025-14270) affecting 1.0.9, so install the newest version.

  3. If you cannot update immediately: deactivate the plugin, or add a WAF rule that blocks unauthenticated requests to the order thank-you endpoint.

  4. Review access logs: look for a single IP requesting the thank-you page with many different order IDs, especially in sequence. That pattern indicates enumeration.

  5. Assess breach obligations: if logs show enumeration, treat it as a personal data breach. Under GDPR Article 33, the controller must notify the supervisory authority within 72 hours of becoming aware, unless the breach is unlikely to result in a risk to individuals.

What should developers learn from it?

Every request for an object must check that the caller is allowed to see that specific object. In WooCommerce, that means confirming ownership for logged-in customers, for example with current_user_can( 'view_order', $order_id ), and validating the order key with $order->key_is_valid( $key ) for guests. Non-sequential or unguessable identifiers reduce enumeration but never replace an authorisation check. Add IDOR test cases to code review and DAST for any endpoint that takes an object ID.

Conclusion

CVE-2025-13526 is simple to exploit and exposes exactly the customer data attackers use for fraud. The fix is a plugin update, but the harder question is whether order data was harvested before you patched.

Your next step: update OneClick Chat to Order to the latest version today, review thank-you page requests in your access logs, and record the decision on breach notification.

Questions and answers

Which versions are affected by CVE-2025-13526?

All versions of the OneClick Chat to Order WordPress plugin up to and including 1.0.8 are affected. Version 1.0.9 fixes the IDOR. Because a separate flaw, CVE-2025-14270, was later reported against 1.0.9, site owners should install the newest available release rather than stopping at 1.0.9.

Does an attacker need an account to exploit CVE-2025-13526?

No. The vulnerability is exploitable by unauthenticated visitors with no user interaction. An attacker only needs to reach the order thank-you page and change the order ID in the URL. This is why the CVSS 3.1 vector records no privileges required and low attack complexity.

Is CVE-2025-13526 being actively exploited?

CISA's November 2025 enrichment recorded no known exploitation, and its EPSS probability has stayed low. That can change, and sequential order IDs make enumeration easy to script, so treat unpatched sites as exposed regardless of current exploitation data.

Are full payment card numbers exposed?

The advisory refers to payment methods, meaning which method the customer chose, not full card data. WooCommerce stores using a payment gateway normally never hold full card numbers. The exposed names, contacts, addresses and order history are still sensitive personal data and valuable for fraud.

How can I tell if my shop was targeted?

Review web server or WAF logs for requests to the order thank-you page. A single IP or small IP range requesting many different order IDs, particularly in sequence and within a short period, indicates enumeration. Compare request times against your update date to bound the exposure window.

Do I need to report exposure under GDPR?

If you find evidence that customer data was accessed, it is likely a personal data breach. GDPR Article 33 requires notifying the supervisory authority within 72 hours of becoming aware, unless the breach is unlikely to result in a risk to individuals. Document the assessment either way and seek legal advice for your case.

Sources

  1. Wordfence
0 comments

Discussion

Report an issue with this article

Spotted an error, outdated advice, a security concern or a broken link? Tell me and I'll review and fix it.

Only used to reply to you about this report.