{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-9864 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-9864 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-9864 is a medium-severity vulnerability in n/a, published on 28 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-9864 and fix it if it is affected.\n\nWhat it is: CVE-2019-9864 is a medium-severity vulnerability in n/a, published on 28 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-9864 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2019-9864/ (Markdown: https://insights.sbomify.com/CVE-2019-9864/index.md)","id":"CVE-2019-9864","markdown":"https://insights.sbomify.com/CVE-2019-9864/index.md","name":"CVE-2019-9864","record":{"aliases":["GHSA-f97c-6p24-qc68"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"PHP e-commerce script","requires_auth":"low_privilege","summary":"Attackers can tamper with payment amounts in the Amazon Affiliate Store script, leading to financial loss or unauthorized transactions.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"amazon_affiliate_store","vendor":"amazon_affiliate_store_project"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[],"description":"PHP Scripts Mall Amazon Affiliate Store 2.1.6 allows Parameter Tampering of the payment amount.","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":"Business logic in n/a","id":"CVE-2019-9864","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Integer overflow in n/a","id":"CVE-2019-9865"},"packages":[],"prev":{"headline":"Weak cryptography in n/a","id":"CVE-2019-9863"},"products":["n/a"],"published":"2019-03-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can tamper with payment amounts in the Amazon Affiliate Store script, leading to financial loss or unauthorized transactions.","url":"https://insights.sbomify.com/CVE-2019-9864/"}