{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-103313 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-103313 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-103313 is a medium-severity vulnerability in Unknown BitPay Gateway for WooCommerce, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-103313 and fix it if it is affected.\n\nWhat it is: CVE-2026-103313 is a medium-severity vulnerability in Unknown BitPay Gateway for WooCommerce, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-103313 in the wild and no public exploit code.\n\nAffected product: Unknown BitPay Gateway for WooCommerce. 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-103313/ (Markdown: https://insights.sbomify.com/CVE-2026-103313/index.md)","id":"CVE-2026-103313","markdown":"https://insights.sbomify.com/CVE-2026-103313/index.md","name":"CVE-2026-103313","record":{"aliases":["GHSA-m8g2-r2r9-qg3j"],"analysis":null,"analysis_generated_by":null,"assigner":"WPScan","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"The BitPay Gateway for WooCommerce WordPress plugin through 4.1.3 does not bind the payment provider's transaction confirmation to the order it completes, nor verify the confirmed amount, allowing an unauthenticated attacker who holds a single genuine low-value transaction to mark arbitrary higher-value orders as paid.","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":"BitPay Gateway for WooCommerce \u003c= 4.1.3 - Unauthenticated Payment Bypass via Payment Return Handler","id":"CVE-2026-103313","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Stackrox: stackrox: saml response replay allows multiple central authentication tokens","id":"CVE-2026-103314"},"packages":[],"prev":{"headline":"Payment Integration Wompi \u003c= 4.0.1 - Unauthenticated Payment Confirmation Forgery via IPN Callback","id":"CVE-2026-103312"},"products":["BitPay Gateway for WooCommerce"],"published":"2026-10-28","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-28","vendors":["Unknown"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-103313/"}