Flow Payment
Approved changes feed: RSS · Atom
cpe:2.3:a:flow:flow_payment:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Flow (ca606d1b-55c9-5a2a-bea8-141873370002) |
|---|---|
| Product | Flow Payment (06132ff5-1eda-53ba-b077-d62bd4eb90ae) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-57857 |
vulnerable | 2026-07-29 01:03:16.365533 |
Flow Payment Plugin for WordPress Reflected Cross-Site Scripting via error_message Parameter
MEDIUM (4.3)
The Flow Payment plugin for WordPress (flow.cl) version 3.0.8 is vulnerable to reflected cross-site scripting on the WooCommerce checkout page. When the plugin handles an order cancellation, the error_message GET parameter is passed directly to wc_add_notice() in flowpayment-fl.php (lines 57-58) without input sanitization (for example sanitize_text_field()) or output escaping (for example esc_html()) before being rendered in the checkout notice HTML. An unauthenticated attacker can craft a URL containing a JavaScript payload in the error_message parameter (for example /checkout/?add-to-cart={product-id}&cancel_order=true&error_message={payload}); when a victim with an active WooCommerce checkout session follows the link, the payload executes in the victim's browser in the origin of the WordPress site.
Published: 2026-07-18T20:33:06.674Z
Updated: 2026-07-20T17:45:54.451Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.