{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-16252 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-16252 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-16252 is a low-severity vulnerability in n/a, published on 5 Sep 2018. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-16252 and fix it if it is affected.\n\nWhat it is: CVE-2018-16252 is a low-severity vulnerability in n/a, published on 5 Sep 2018. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-16252 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-16252/ (Markdown: https://insights.sbomify.com/CVE-2018-16252/index.md)","id":"CVE-2018-16252","markdown":"https://insights.sbomify.com/CVE-2018-16252/index.md","name":"CVE-2018-16252","record":{"aliases":["GHSA-g939-wpmq-66q4"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Event Log Explorer","requires_auth":"low_privilege","summary":"An attacker can exploit XML External Entity injection in Event Log Explorer via malicious .elx files to read sensitive data or cause denial of service.","user_interaction":"not_required","vuln_class":"xxe"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"event_log_explorer","vendor":"fspro"}],"cvss":{"score":3.3,"severity":"low","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-611","name":"Improper Restriction of XML External Entity Reference"}],"description":"FsPro Labs Event Log Explorer 4.6.1.2115 has \".elx\" FileType XML External Entity Injection.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2018-09-03","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2018-09-03","kind":"exploitdb","ref":"45319","stars":null,"title":"FsPro Labs Event Log Explorer v4.6.1.2115 - XML External Entity Injection"}],"tier":"poc_unverified"},"has_fix":null,"headline":"XML external entity in n/a","id":"CVE-2018-16252","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xxe","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2018-16253"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2018-16251"},"products":["n/a"],"published":"2018-09-05","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":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"An attacker can exploit XML External Entity injection in Event Log Explorer via malicious .elx files to read sensitive data or cause denial of service.","url":"https://insights.sbomify.com/CVE-2018-16252/"}