{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-57857 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-57857 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-57857 is a medium-severity cross-site scripting vulnerability in Flow Payment, published on 18 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-57857 and fix it if it is affected.\n\nWhat it is: CVE-2026-57857 is a medium-severity cross-site scripting vulnerability in Flow Payment, published on 18 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-57857 in the wild and no public exploit code.\n\nAffected product: Flow Payment. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-57857/ (Markdown: https://insights.sbomify.com/CVE-2026-57857/index.md)","id":"CVE-2026-57857","markdown":"https://insights.sbomify.com/CVE-2026-57857/index.md","name":"CVE-2026-57857","record":{"aliases":["GHSA-r6hg-r245-924g"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress payment plugin","requires_auth":"none","summary":"An unauthenticated attacker can execute arbitrary JavaScript in a victim's browser via a crafted URL on the WooCommerce checkout page.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"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}\u0026cancel_order=true\u0026error_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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Flow Payment Plugin for WordPress Reflected Cross-Site Scripting via error_message Parameter","id":"CVE-2026-57857","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Cal.com Cal.diy 6.2.0 Stored XSS via BookingPageTagManager Analytics Tracking ID","id":"CVE-2026-57858"},"packages":[],"prev":{"headline":"Cockpit CMS Path Traversal via Bucket Name in Bucket File Storage API","id":"CVE-2026-57856"},"products":["Flow Payment"],"published":"2026-07-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-20","vendors":["Flow"]},"summary":"An unauthenticated attacker can execute arbitrary JavaScript in a victim's browser via a crafted URL on the WooCommerce checkout page.","url":"https://insights.sbomify.com/CVE-2026-57857/"}