{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-16386 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-16386 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-16386 is a medium-severity vulnerability in n/a, published on 26 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-16386 and fix it if it is affected.\n\nWhat it is: CVE-2019-16386 is a medium-severity vulnerability in n/a, published on 26 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-16386 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-2019-16386/ (Markdown: https://insights.sbomify.com/CVE-2019-16386/index.md)","id":"CVE-2019-16386","markdown":"https://insights.sbomify.com/CVE-2019-16386/index.md","name":"CVE-2019-16386","record":{"aliases":["GHSA-5ch4-c735-4f8x"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"PEGA Platform","requires_auth":"low_privilege","summary":"An attacker with low privileges could potentially access database schema information via a specific web request, though the vendor disputes the privilege level required.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pega_platform","vendor":"pega"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-425","name":"Direct Request"}],"description":"PEGA Platform 7.x and 8.x is vulnerable to Information disclosure via a direct prweb/sso/random_token/!STANDARD?pyActivity=GetWebInfo\u0026target=popup\u0026pzHarnessID=random_harness_id request to get database schema information while using a low-privilege account. NOTE: The vendor states that this vulnerability was discovered using an administrator account and they are normal administrator functions. Therefore, the claim that the CVE was done with a low privilege account is incorrect","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2019-16386","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in n/a","id":"CVE-2019-16387"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-16385"},"products":["n/a"],"published":"2019-11-26","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in Pega Platform","id":"CVE-2023-32090","kev_date_added":null,"published":"2023-08-07"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2020-15390","kev_date_added":null,"published":"2021-04-12"},{"cvss_score":8.8,"headline":"Cross-site scripting in n/a","id":"CVE-2020-8774","kev_date_added":null,"published":"2020-04-29"},{"cvss_score":8.1,"headline":"Cross-site scripting in Pega Infinity","id":"CVE-2025-2160","kev_date_added":null,"published":"2025-04-14"},{"cvss_score":8.1,"headline":"Hardcoded credentials in Pega Platform","id":"CVE-2023-28094","kev_date_added":null,"published":"2023-06-22"},{"cvss_score":8.1,"headline":"Missing authorization in n/a","id":"CVE-2019-16387","kev_date_added":null,"published":"2019-11-26"},{"cvss_score":8,"headline":"Cross-site scripting in Pega Infinity","id":"CVE-2023-26465","kev_date_added":null,"published":"2023-06-09"}],"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":"An attacker with low privileges could potentially access database schema information via a specific web request, though the vendor disputes the privilege level required.","url":"https://insights.sbomify.com/CVE-2019-16386/"}