{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-15555 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-15555 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-15555 is a critical SQL injection vulnerability in n/a, published on 26 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-15555 and fix it if it is affected.\n\nWhat it is: CVE-2019-15555 is a critical SQL injection vulnerability in n/a, published on 26 Aug 2019. 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-2019-15555 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-15555/ (Markdown: https://insights.sbomify.com/CVE-2019-15555/index.md)","id":"CVE-2019-15555","markdown":"https://insights.sbomify.com/CVE-2019-15555/index.md","name":"CVE-2019-15555","record":{"aliases":["GHSA-fpvq-hm3c-cqwh"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Wellness app","requires_auth":"none","summary":"SQL injection in FredReinink Wellness-app allows attackers to read or modify database contents via vulnerable PHP scripts.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wellness","vendor":"wellness_project"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"FredReinink Wellness-app before 2019-06-19 allows SQL injection, related to dietTrack.php, exerciseGenerator.php, fitnessTrack.php, and server.php.","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":"SQL injection in n/a","id":"CVE-2019-15555","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2019-15556"},"packages":[],"prev":{"headline":"Memory corruption in smallvec","id":"CVE-2019-15554"},"products":["n/a"],"published":"2019-08-26","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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"SQL injection in FredReinink Wellness-app allows attackers to read or modify database contents via vulnerable PHP scripts.","url":"https://insights.sbomify.com/CVE-2019-15555/"}