{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-5504 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-5504 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-5504 is a medium-severity vulnerability in n/a, published on 25 Oct 2016. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-5504 and fix it if it is affected.\n\nWhat it is: CVE-2016-5504 is a medium-severity vulnerability in n/a, published on 25 Oct 2016. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2016-5504 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-2016-5504/ (Markdown: https://insights.sbomify.com/CVE-2016-5504/index.md)","id":"CVE-2016-5504","markdown":"https://insights.sbomify.com/CVE-2016-5504/index.md","name":"CVE-2016-5504","record":{"aliases":["GHSA-jfrv-59mj-p5v7"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Oracle Agile PLM","requires_auth":"high_privilege","summary":"Local users can access sensitive information in Oracle Agile PLM Supplier Portal, requiring a patch to prevent data leakage.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"oracle","cpe":[{"product":"agile_product_lifecycle_management_for_process","vendor":"oracle"}],"cvss":{"score":4.1,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Unspecified vulnerability in the Oracle Agile Product Lifecycle Management for Process component in Oracle Supply Chain Products Suite 6.1.0.4, 6.1.1.6, and 6.2.0.0 allows local users to affect confidentiality via vectors related to Supplier Portal.","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-2016-5504","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2016"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2016-5505"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2016-5503"},"products":["n/a"],"published":"2016-10-25","related":[{"cvss_score":9.8,"headline":"Auth bypass in Oracle Agile Product Lifecycle Management for Process","id":"CVE-2026-61178","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":9.8,"headline":"Auth bypass in Oracle Agile Product Lifecycle Management for Process","id":"CVE-2026-61183","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":9.8,"headline":"Auth bypass in Oracle Agile Product Lifecycle Management for Process","id":"CVE-2026-21969","kev_date_added":null,"published":"2026-01-20"},{"cvss_score":9.1,"headline":"Missing authorization in Oracle Agile Product Lifecycle Management for Process","id":"CVE-2026-61184","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":8.8,"headline":"Auth bypass in Oracle Agile Product Lifecycle Management for Process","id":"CVE-2026-61179","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":8.8,"headline":"Auth bypass in Oracle Agile Product Lifecycle Management for Process","id":"CVE-2026-61180","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":8.1,"headline":"Missing authorization in Agile Product Lifecycle Management for Process","id":"CVE-2024-21092","kev_date_added":null,"published":"2024-04-16"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-10","vendors":["n/a"]},"summary":"Local users can access sensitive information in Oracle Agile PLM Supplier Portal, requiring a patch to prevent data leakage.","url":"https://insights.sbomify.com/CVE-2016-5504/"}