{"answers":{"affected":"2 open source packages ship an affected version, including gleez/cms. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1999021 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-1999021 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-1999021 is a medium-severity cross-site scripting vulnerability in n/a, published on 23 Jul 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-1999021 and fix it if it is affected.\n\nWhat it is: CVE-2018-1999021 is a medium-severity cross-site scripting vulnerability in n/a, published on 23 Jul 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-1999021 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- gleez/cms (Packagist): affected all versions up to 1.3.0; no fix listed\n- gleez/cms (Packagist): affected all versions up to 1.3.0; no fix listed\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-1999021/ (Markdown: https://insights.sbomify.com/CVE-2018-1999021/index.md)","id":"CVE-2018-1999021","markdown":"https://insights.sbomify.com/CVE-2018-1999021/index.md","name":"CVE-2018-1999021","record":{"aliases":["GHSA-q9g7-pff4-548r"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Gleez CMS","requires_auth":"low_privilege","summary":"An attacker can inject arbitrary web script or HTML via the profile page editor, potentially executing code in the victim's browser.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gleezcms","vendor":"gleeztech"}],"cvss":{"score":5.4,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Gleezcms Gleez Cms version 1.3.0 contains a Cross Site Scripting (XSS) vulnerability in Profile page that can result in Inject arbitrary web script or HTML via the profile page editor. This attack appear to be exploitable via The victim must navigate to the attacker's profile page.","ecosystems":["Packagist"],"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":"Gleez Cms Cross-site Scripting in Profile Page","id":"CVE-2018-1999021","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"xss","year":"2018"},"n_packages":2,"n_references":1,"next":{"headline":"Code injection in n/a","id":"CVE-2018-1999022"},"packages":[{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["1.3.0"],"package":"gleez/cms","purl":null,"source":"GHSA-q9g7-pff4-548r"},{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["1.3.0"],"package":"gleez/cms","purl":"pkg:composer/gleez/cms","source":"GHSA-q9g7-pff4-548r"}],"prev":{"headline":"Path traversal in n/a","id":"CVE-2018-1999020"},"products":["n/a"],"published":"2018-07-23","related":[{"cvss_score":4.3,"headline":"Gleez CMS Vulnerability Allows Forced Browsing to Profile Page of Other Users","id":"CVE-2018-16704","kev_date_added":null,"published":"2018-09-07"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"An attacker can inject arbitrary web script or HTML via the profile page editor, potentially executing code in the victim's browser.","url":"https://insights.sbomify.com/CVE-2018-1999021/"}