{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-103299 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-103299 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-103299 is a vulnerability in Unknown Payment Gateway, published on 26 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-103299 and fix it if it is affected.\n\nWhat it is: CVE-2026-103299 is a vulnerability in Unknown Payment Gateway, published on 26 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-103299 in the wild and no public exploit code.\n\nAffected product: Unknown Payment Gateway. 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-103299/ (Markdown: https://insights.sbomify.com/CVE-2026-103299/index.md)","id":"CVE-2026-103299","markdown":"https://insights.sbomify.com/CVE-2026-103299/index.md","name":"CVE-2026-103299","record":{"aliases":["GHSA-3fmh-h32q-9jjr"],"analysis":null,"analysis_generated_by":null,"assigner":"WPScan","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"The Payment Gateway  WordPress plugin through 2.2.0 does not ensure a shared secret is configured before using it to authenticate the bank's payment-notification callback, allowing unauthenticated attackers to forge a valid notification and mark any WooCommerce order as paid on installs where the secret has not been set, and the same callback lets them move any pending order to a failed state whether or not the secret is configured.","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":"nexi Alpha Bank for WooCommerce \u003c= 2.2.0 - Unauthenticated Payment Confirmation Forgery via Empty Shared Secret","id":"CVE-2026-103299","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Eurobank WooCommerce Payment Gateway \u003c= 2.1.1 - Unauthenticated Order Payment Forgery via Unverified Callback","id":"CVE-2026-103300"},"packages":[],"prev":{"headline":"CCAvenue Payment Gateway for WooCommerce \u003c= 3.1 - Unauthenticated Order Payment Completion via Webhook Forgery","id":"CVE-2026-103298"},"products":["Payment Gateway"],"published":"2026-10-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-26","vendors":["Unknown"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-103299/"}