{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-46018 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-46018 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-46018 is a medium-severity vulnerability in n/a, published on 1 Aug 2025. 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-2025-46018 and fix it if it is affected.\n\nWhat it is: CVE-2025-46018 is a medium-severity vulnerability in n/a, published on 1 Aug 2025. 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-2025-46018 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-2025-46018/ (Markdown: https://insights.sbomify.com/CVE-2025-46018/index.md)","id":"CVE-2025-46018","markdown":"https://insights.sbomify.com/CVE-2025-46018/index.md","name":"CVE-2025-46018","record":{"aliases":["GHSA-v6qp-r53v-fvh5"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["security_bypass","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"CSC Pay Mobile App","requires_auth":"none","summary":"Attackers can bypass payment authorization in CSC Pay Mobile App by disabling Bluetooth during transactions, leading to unauthorized service use.","user_interaction":"required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pay_mobile","vendor":"cscsw"}],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"description":"CSC Pay Mobile App 2.19.4 (fixed in version 2.20.0) contains a vulnerability allowing users to bypass payment authorization by disabling Bluetooth at a specific point during a transaction. This could result in unauthorized use of laundry services and potential financial loss.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-08-01","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-08-01T12:25:01Z","kind":"github_poc","ref":"https://github.com/niranjangaire1995/CVE-2025-46018-CSC-Pay-Mobile-App-Payment-Authentication-Bypass","stars":0,"title":"Disclosure of CVE-2025-46018: A Bluetooth-based payment bypass vulnerability in CSC Pay Mobile App v2.19.4\""}],"tier":"poc_unverified"},"has_fix":null,"headline":"Business logic in n/a","id":"CVE-2025-46018","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2025-46035"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2025-46014"},"products":["n/a"],"published":"2025-08-01","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-08-01","vendors":["n/a"]},"summary":"Attackers can bypass payment authorization in CSC Pay Mobile App by disabling Bluetooth during transactions, leading to unauthorized service use.","url":"https://insights.sbomify.com/CVE-2025-46018/"}