PatchSiren cyber security CVE debrief
CVE-2026-57857 Flow CVE debrief
The Flow Payment plugin for WordPress version 3.0.8 is vulnerable to reflected cross-site scripting on the WooCommerce checkout page. An unauthenticated attacker can craft a URL containing a JavaScript payload in the error_message parameter. This vulnerability has a CVSS score of 5.1 and a MEDIUM severity. Users of the Flow Payment plugin for WordPress version 3.0.8 should be aware of this vulnerability and take steps to mitigate it. The vulnerability is caused by the lack of input sanitization and output escaping in the error_message parameter.
- Vendor
- Flow
- Product
- Flow Payment
- CVSS
- MEDIUM 5.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-18
- Original CVE updated
- 2026-07-20
- Advisory published
- 2026-07-18
- Advisory updated
- 2026-07-20
Who should care
Users of the Flow Payment plugin for WordPress version 3.0.8 should be aware of this vulnerability and take steps to mitigate it. This includes applying the latest patch or update to a version that addresses this vulnerability, implementing input sanitization and output escaping for the error_message parameter, and monitoring for suspicious activity on the WooCommerce checkout page.
Technical summary
The Flow Payment plugin for WordPress 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 or output escaping before being rendered in the checkout notice HTML. This allows an unauthenticated attacker to craft a URL containing a JavaScript payload in the error_message parameter.
Defensive priority
Medium priority due to CVSS score of 5.1 and potential impact on WooCommerce checkout page
Recommended defensive actions
- Apply the latest patch or update to a version that addresses this vulnerability
- Implement input sanitization and output escaping for the error_message parameter
- Monitor for suspicious activity on the WooCommerce checkout page
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
Evidence is limited, but the CVE record and NVD detail provide some information about the vulnerability. The CVE record was published on 2026-07-18T21:17:03.687Z and has not been modified since then. Defenders should verify the affected scope and severity based on the official advisory. The error_message GET parameter is passed directly to wc_add_notice() in flowpayment-fl.php (lines 57-58) without input sanitization or output escaping before being rendered in the checkout notice HTML.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-57857 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-57857
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-57857 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-57857
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://www.flow.cl/
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/flow-payment-plugin-for-wordpress-reflected-cross-site-scripting-via-error-message-parameter
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.