{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-11215 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-11215 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-11215 is a high-severity code injection vulnerability in Combodo Itop, published on 14 Feb 2020. 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-11215 and fix it if it is affected.\n\nWhat it is: CVE-2019-11215 is a high-severity code injection vulnerability in Combodo Itop, published on 14 Feb 2020. 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-11215 in the wild and no public exploit code.\n\nAffected product: Combodo Itop. 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-11215/ (Markdown: https://insights.sbomify.com/CVE-2019-11215/index.md)","id":"CVE-2019-11215","markdown":"https://insights.sbomify.com/CVE-2019-11215/index.md","name":"CVE-2019-11215","record":{"aliases":["GHSA-245p-293f-hm6f"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"iTop ITSM application","requires_auth":"none","summary":"Attackers can execute arbitrary code in iTop if the configuration file is writable, a state often caused by installation, upgrades, or XSS-triggered errors.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"itop","vendor":"combodo"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"},{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"In Combodo iTop 2.2.0 through 2.6.0, if the configuration file is writable, then execution of arbitrary code can be accomplished by calling ajax.dataloader with a maliciously crafted payload. Many conditions can place the configuration file into a writable state: during installation; during upgrade; in certain cases, an error during modification of the file from the web interface leaves the file writable (can be triggered with XSS); a race condition can be triggered by the hub-connector module (community version only from 2.4.1 to 2.6.0); or editing the file in a CLI.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Code injection in n/a","id":"CVE-2019-11215","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"combodo:itop","products":["combodo:itop"],"type":"code_injection","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"XML external entity in n/a","id":"CVE-2019-11216"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2019-11213"},"products":["n/a"],"published":"2020-02-14","related":[{"cvss_score":9.8,"headline":"iTop limit pages/exec.php script to PHP files","id":"CVE-2023-48710","kev_date_added":null,"published":"2024-04-15"},{"cvss_score":9.6,"headline":"Authenticated users of Combodo iTop can take over any account","id":"CVE-2022-39214","kev_date_added":null,"published":"2023-03-14"},{"cvss_score":9.3,"headline":"XSS in csvimport in 3.0.0-beta versions","id":"CVE-2021-41161","kev_date_added":null,"published":"2022-04-21"},{"cvss_score":9.3,"headline":"Cross-site Scripting in Combodo iTop","id":"CVE-2021-41162","kev_date_added":null,"published":"2022-04-21"},{"cvss_score":8.8,"headline":"Combodo iTop has XSS vulnerability in /pages/ajax.render.php","id":"CVE-2025-47773","kev_date_added":null,"published":"2025-11-10"},{"cvss_score":8.8,"headline":"Combodo iTop vulnerable to reflected XSS in ajax.render.php render_dashboard","id":"CVE-2025-47932","kev_date_added":null,"published":"2025-11-10"},{"cvss_score":8.8,"headline":"Combodo iTop vulnerable to reflected XSS via objection edition form error","id":"CVE-2025-48065","kev_date_added":null,"published":"2025-11-10"}],"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-04","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code in iTop if the configuration file is writable, a state often caused by installation, upgrades, or XSS-triggered errors.","url":"https://insights.sbomify.com/CVE-2019-11215/"}