{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-16703 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-16703 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-16703 is a medium-severity vulnerability in n/a, published on 7 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-16703 and fix it if it is affected.\n\nWhat it is: CVE-2018-16703 is a medium-severity vulnerability in n/a, published on 7 Sep 2018. 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-2018-16703 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-16703/ (Markdown: https://insights.sbomify.com/CVE-2018-16703/index.md)","id":"CVE-2018-16703","markdown":"https://insights.sbomify.com/CVE-2018-16703/index.md","name":"CVE-2018-16703","record":{"aliases":["GHSA-hj39-q7cj-vfhf"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Gleez CMS","requires_auth":"none","summary":"Unauthenticated attackers can enumerate users and bypass login attempt limits in Gleez CMS, facilitating brute-force attacks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gleez_cms","vendor":"gleeztech"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"},{"id":"CWE-521","name":"Weak Password Requirements"},{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"}],"description":"A vulnerability in the Gleez CMS 1.2.0 login page could allow an unauthenticated, remote attacker to perform multiple user enumerations, which can further help an attacker to perform login attempts in excess of the configured login attempt limit. The vulnerability is due to insufficient server-side access control and login attempt limit enforcement. An attacker could exploit this vulnerability by sending modified login attempts to the Portal login page. An exploit could allow the attacker to identify existing users and perform brute-force password attacks on the Portal, as demonstrated by navigating to the user/4 URI.","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":"Information disclosure in n/a","id":"CVE-2018-16703","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Gleez CMS Vulnerability Allows Forced Browsing to Profile Page of Other Users","id":"CVE-2018-16704"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2018-16672"},"products":["n/a"],"published":"2018-09-07","related":[{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-13340","kev_date_added":null,"published":"2018-07-05"}],"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-05","vendors":["n/a"]},"summary":"Unauthenticated attackers can enumerate users and bypass login attempt limits in Gleez CMS, facilitating brute-force attacks.","url":"https://insights.sbomify.com/CVE-2018-16703/"}