{"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-16704 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-16704 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-16704 is a medium-severity vulnerability in n/a, published on 7 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-16704 and fix it if it is affected.\n\nWhat it is: CVE-2018-16704 is a medium-severity vulnerability in n/a, published on 7 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-16704 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- gleez/cms (Packagist): affected all versions up to 1.2.0; no fix listed\n- gleez/cms (Packagist): affected all versions up to 1.2.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-16704/ (Markdown: https://insights.sbomify.com/CVE-2018-16704/index.md)","id":"CVE-2018-16704","markdown":"https://insights.sbomify.com/CVE-2018-16704/index.md","name":"CVE-2018-16704","record":{"aliases":["GHSA-hh92-wg7v-8vfr"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Gleez CMS","requires_auth":"low_privilege","summary":"Logged-in users can view other users' profile pages via insecure direct object reference, exposing private user data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gleezcms","vendor":"gleeztech"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"An issue was discovered in Gleez CMS v1.2.0. Because of an Insecure Direct Object Reference vulnerability, it is possible for attackers (logged in users) to view profile page of other users, as demonstrated by navigating to user/3 on demo.gleezcms.org.","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 Vulnerability Allows Forced Browsing to Profile Page of Other Users","id":"CVE-2018-16704","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":2,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2018-16705"},"packages":[{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["1.2.0"],"package":"gleez/cms","purl":null,"source":"GHSA-hh92-wg7v-8vfr"},{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["1.2.0"],"package":"gleez/cms","purl":"pkg:composer/gleez/cms","source":"GHSA-hh92-wg7v-8vfr"}],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2018-16703"},"products":["n/a"],"published":"2018-09-07","related":[{"cvss_score":5.4,"headline":"Gleez Cms Cross-site Scripting in Profile Page","id":"CVE-2018-1999021","kev_date_added":null,"published":"2018-07-23"}],"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-08-05","vendors":["n/a"]},"summary":"Logged-in users can view other users' profile pages via insecure direct object reference, exposing private user data.","url":"https://insights.sbomify.com/CVE-2018-16704/"}