{"answers":{"affected":"2 open source packages ship an affected version, including pagekit/pagekit. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-16669 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-16669 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-16669 is a medium-severity vulnerability in n/a, published on 21 Sep 2019. 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-16669 and fix it if it is affected.\n\nWhat it is: CVE-2019-16669 is a medium-severity vulnerability in n/a, published on 21 Sep 2019. 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-16669 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pagekit/pagekit (Packagist): affected all versions; no fix listed\n- pagekit/pagekit (Packagist): affected all versions; 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-2019-16669/ (Markdown: https://insights.sbomify.com/CVE-2019-16669/index.md)","id":"CVE-2019-16669","markdown":"https://insights.sbomify.com/CVE-2019-16669/index.md","name":"CVE-2019-16669","record":{"aliases":["GHSA-jh2j-7248-9p3c"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Pagekit CMS","requires_auth":"none","summary":"Attackers can enumerate valid user accounts via inconsistent responses in the password reset feature, facilitating targeted attacks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pagekit","vendor":"pagekit"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"}],"description":"The Reset Password feature in Pagekit 1.0.17 gives a different response depending on whether the e-mail address of a valid user account is entered, which might make it easier for attackers to enumerate accounts.","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":"Pagekit User enumeration","id":"CVE-2019-16669","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":2,"n_references":1,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2019-16670"},"packages":[{"ecosystem":"Packagist","fixed":[],"introduced":[],"last_affected":[],"package":"pagekit/pagekit","purl":null,"source":"GHSA-jh2j-7248-9p3c"},{"ecosystem":"Packagist","fixed":[],"introduced":[],"last_affected":[],"package":"pagekit/pagekit","purl":"pkg:composer/pagekit/pagekit","source":"GHSA-jh2j-7248-9p3c"}],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2019-16667"},"products":["n/a"],"published":"2019-09-21","related":[{"cvss_score":9.9,"headline":"Pagekit CMS is vulnerable to OS Command Injection via Storage component","id":"CVE-2025-67164","kev_date_added":null,"published":"2025-12-17"},{"cvss_score":9.8,"headline":"Pagekit CMS has an Insecure Direct Object Reference (IDOR) in its User Role component","id":"CVE-2025-67165","kev_date_added":null,"published":"2025-12-17"},{"cvss_score":9.8,"headline":"Pagekit vulnerable to Unrestricted Upload of File with Dangerous Type","id":"CVE-2022-38916","kev_date_added":null,"published":"2022-09-20"},{"cvss_score":9.8,"headline":"SQL injection in pagekit/pagekit","id":"CVE-2021-44135","kev_date_added":null,"published":"2022-04-01"},{"cvss_score":8.8,"headline":"Pagekit File Upload vulnerability","id":"CVE-2019-19013","kev_date_added":null,"published":"2019-11-22"},{"cvss_score":7.8,"headline":"Command injection in pagekit","id":"CVE-2023-41005","kev_date_added":null,"published":"2023-08-28"},{"cvss_score":7.5,"headline":"Pagekit Weak Password Recovery Mechanism for Forgotten Password","id":"CVE-2017-5594","kev_date_added":null,"published":"2017-01-25"}],"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":"Attackers can enumerate valid user accounts via inconsistent responses in the password reset feature, facilitating targeted attacks.","url":"https://insights.sbomify.com/CVE-2019-16669/"}