{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-103330 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-103330 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-103330 is a medium-severity vulnerability in Unknown Sadad QA Payment, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-103330 and fix it if it is affected.\n\nWhat it is: CVE-2026-103330 is a medium-severity vulnerability in Unknown Sadad QA Payment, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-103330 in the wild and no public exploit code.\n\nAffected product: Unknown Sadad QA 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-103330/ (Markdown: https://insights.sbomify.com/CVE-2026-103330/index.md)","id":"CVE-2026-103330","markdown":"https://insights.sbomify.com/CVE-2026-103330/index.md","name":"CVE-2026-103330","record":{"aliases":["GHSA-6pxp-6v4v-67f3"],"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 Sadad QA Payment WordPress plugin through 1.28 does not correctly verify the authenticity of incoming payment notifications, as the verification is keyed on a merchant secret that is empty by default and the rest of the signed data is attacker-controlled, allowing unauthenticated attackers to forge a valid confirmation and mark orders as paid without payment.","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":"Sadad QA Payment 1.28 - Unauthenticated Arbitrary Order Payment Confirmation via Signature Bypass","id":"CVE-2026-103330","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"UniPAY Payment Gateway For WooCommerce \u003c= 2.3 - Unauthenticated Order Payment Forgery via Empty IPN Secret","id":"CVE-2026-103331"},"packages":[],"prev":{"headline":"Super Payments \u003c 1.43.1 - Unauthenticated Payment Confirmation Forgery via Webhook Signature","id":"CVE-2026-103329"},"products":["Sadad QA Payment"],"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-103330/"}