{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-19654 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-19654 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-19654 is a high-severity vulnerability in n/a, published on 29 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-19654 and fix it if it is affected.\n\nWhat it is: CVE-2018-19654 is a high-severity vulnerability in n/a, published on 29 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-19654 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-2018-19654/ (Markdown: https://insights.sbomify.com/CVE-2018-19654/index.md)","id":"CVE-2018-19654","markdown":"https://insights.sbomify.com/CVE-2018-19654/index.md","name":"CVE-2018-19654","record":{"aliases":["GHSA-pj3r-6hh7-8pcg"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Sales Management System","requires_auth":"none","summary":"Attackers can register duplicate usernames due to inconsistent validation between string checks and database queries, compromising account integrity.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sales_\\\u0026_company_management_system","vendor":"sales_\\\u0026_company_management_system_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"An issue was discovered in Sales \u0026 Company Management System (SCMS) through 2018-06-06. There is a discrepancy in username checking between a component that does string validation, and a component that is supposed to query a MySQL database. Thus, it is possible to register a new account with a duplicate username, as demonstrated by use of the test%c2 string when a test account already exists.","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-2018-19654","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2018-19655"},"packages":[],"prev":{"headline":"HashiCorp Consul can use cleartext agent-to-agent RPC communication","id":"CVE-2018-19653"},"products":["n/a"],"published":"2018-11-29","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2018-19925","kev_date_added":null,"published":"2018-12-06"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-19923","kev_date_added":null,"published":"2018-12-06"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2018-19924","kev_date_added":null,"published":"2018-12-06"}],"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can register duplicate usernames due to inconsistent validation between string checks and database queries, compromising account integrity.","url":"https://insights.sbomify.com/CVE-2018-19654/"}