{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-7720 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-7720 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-7720 is a critical code injection vulnerability in n/a, published on 11 Feb 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-7720 and fix it if it is affected.\n\nWhat it is: CVE-2019-7720 is a critical code injection vulnerability in n/a, published on 11 Feb 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-7720 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-7720/ (Markdown: https://insights.sbomify.com/CVE-2019-7720/index.md)","id":"CVE-2019-7720","markdown":"https://insights.sbomify.com/CVE-2019-7720/index.md","name":"CVE-2019-7720","record":{"aliases":["GHSA-63pw-526x-mrr6"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"taocms","requires_auth":"none","summary":"Attackers can execute arbitrary PHP code by injecting payloads into the install.php db_name parameter, leading to full system compromise.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"taocms","vendor":"taogogo"}],"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-94","name":"Improper Control of Generation of Code"}],"description":"taocms through 2014-05-24 allows eval injection by placing PHP code in the install.php db_name parameter and then making a config.php request.","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":"Code injection in n/a","id":"CVE-2019-7720","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"File upload in n/a","id":"CVE-2019-7721"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2019-7719"},"products":["n/a"],"published":"2019-02-11","related":[{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2024-33350","kev_date_added":null,"published":"2024-04-29"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2022-48006","kev_date_added":null,"published":"2023-01-30"},{"cvss_score":9.8,"headline":"Server-side request forgery in n/a","id":"CVE-2022-46998","kev_date_added":null,"published":"2023-01-25"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2022-36262","kev_date_added":null,"published":"2022-08-15"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2022-23880","kev_date_added":null,"published":"2022-03-23"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-25505","kev_date_added":null,"published":"2022-03-21"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2022-25578","kev_date_added":null,"published":"2022-03-18"}],"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-09-16","vendors":["n/a"]},"summary":"Attackers can execute arbitrary PHP code by injecting payloads into the install.php db_name parameter, leading to full system compromise.","url":"https://insights.sbomify.com/CVE-2019-7720/"}