STRABL <= 4.5 - Unauthenticated Arbitrary Webhook Creation via REST API Endpoint

5.3
Missing Authorization
CVE CVE-2026-3640
CVSS 5.3 (Medium)
Publicly Published June 18, 2026
Last Updated June 19, 2026
Researcher Teerachai Somprasong

Description

The STRABL – A checkout solution plugin for WordPress is vulnerable to Missing Authentication in all versions up to and including 4.5. The plugin registers a REST API webhook endpoint at /wp-json/strabl/webhook/order with a permission_callback of __return_true, which allows all incoming requests without any authentication or authorization checks. No shared secret, signature validation, HMAC verification, or token-based authentication is implemented. This makes it possible for unauthenticated attackers to create fraudulent WooCommerce orders and mark them as completed by supplying paymentStatus=paid, manipulate existing order statuses by providing an externalOrderId, create new WordPress user accounts with the customer role, issue refunds on existing orders, cancel existing orders, and apply chargeback fees — all without making a legitimate payment or having any valid credentials.

References

Share

Vulnerability Details for STRABL – A checkout solution

Software Type Plugin
Software Slug strabl-a-checkout-solution (view on wordpress.org)
Patched? Yes
Remediation Update to version 4.6, or a newer patched version
Affected Version
  • <= 4.5
Patched Version
  • 4.6

Did you know Wordfence Intelligence provides free personal and commercial API access to our comprehensive WordPress vulnerability database, along with a free webhook integration to stay on top of the latest vulnerabilities added and updated in the database? Get started today!

Learn more

Want to get notified of the latest vulnerabilities that may affect your WordPress site?
Install Wordfence on your site today to get notified immediately if your site is affected by a vulnerability that has been added to our database.

Get Wordfence

The Wordfence Intelligence WordPress vulnerability database is completely free to access and query via API. Please review the documentation on how to access and consume the vulnerability data via API.

Documentation