WordPress security by component
Payment Gateway Based Fees and Discounts for WooCommerce
Plugin description
Payment Gateway Based Fees and Discounts for WooCommerce is a WordPress component with 2 published CVE records in this archive. The latest tracked vulnerability was published Jun 26, 2026; the highest published CVSS base score is 6.5.
Plugin slug:
checkout-fees-for-woocommerceLatest vulnerability
CVE-2026-56048: Payment Gateway Based Fees and Discounts for WooCommerce: Broken access control
Payment Gateway Based Fees and Discounts for WooCommerce is affected by broken access control. The vulnerable path is reachable without authentication. A successful request can reach data or an operation that should be restricted to another user or a more privileged role. The published affected range is n/a through 3.0.0. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
| Safe version |
|
||
|---|---|---|---|
| Jun 26, 2026 |
CVE-2026-56048
Payment Gateway Based Fees and Discounts for WooCommerce: Broken access control
Payment Gateway Based Fees and Discounts for WooCommerce is affected by broken access control. The vulnerable path is reachable without authentication. A successful request can reach data or an operation that should be restricted to another user or a more privileged role. The published affected range is n/a through 3.0.0. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
3.1.0 |
CVE6.5
NVDPending
|
| Apr 29, 2024 |
CVE-2024-33585
Payment Gateway Based Fees and Discounts for WooCommerce: A security weakness
Payment Gateway Based Fees and Discounts for WooCommerce is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE4.3
NVDPending
|