← WordPress Vulnerabilities
WordPress security by component

Flexible Refund and Return Order for WooCommerce

Flexible Refund and Return Order for WooCommerce manages refund and return requests for WooCommerce orders.

Flexible Refund and Return Order for WooCommerce (flexible-refund-and-return-order-for-woocommerce) is a WordPress plugin with 3 published CVE records in this archive. The latest tracked vulnerability was published Jul 13, 2026; the highest published CVSS base score is 6.5.

Plugin slug: flexible-refund-and-return-order-for-woocommerce

CVE-2026-57402: Flexible Refund and Return Order for WooCommerce: Cross-site scripting

Flexible Refund and Return Order for WooCommerce is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The published affected range is <= 1.0.51.

PublishedJul 13, 2026
Known safe version1.0.52
Published vulnerabilities for flexible-refund-and-return-order-for-woocommerce
Safe version
Jul 13, 2026 CVE-2026-57402
Flexible Refund and Return Order for WooCommerce: Cross-site scripting
Flexible Refund and Return Order for WooCommerce is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The published affected range is <= 1.0.51.
1.0.52
CVE6.5
Nov 08, 2025 CVE-2025-12621
Flexible Refund and Return Order for WooCommerce: A security weakness
Flexible Refund and Return Order for WooCommerce is affected by a security weakness. Exploitation requires an authenticated contributor account. The resulting impact depends on how the affected component exposes the vulnerable operation.
See mitigation notes
CVE5.3
Oct 22, 2025 CVE-2025-10570
Flexible Refund and Return Order for WooCommerce: A security weakness
Flexible Refund and Return Order for WooCommerce is affected by a security weakness. Exploitation requires an authenticated subscriber account. The resulting impact depends on how the affected component exposes the vulnerable operation.
See mitigation notes
CVE4.3