{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5177 exists.","fix":"No fix has been published for CVE-2023-5177 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-5177 is a medium-severity vulnerability in Unknown Vrm 360 3D Model Viewer, published on 16 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-5177 and fix it if it is affected.\n\nWhat it is: CVE-2023-5177 is a medium-severity vulnerability in Unknown Vrm 360 3D Model Viewer, published on 16 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5177 exists.\n\nAffected product: Unknown Vrm 360 3D Model Viewer. 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-2023-5177/ (Markdown: https://insights.sbomify.com/CVE-2023-5177/index.md)","id":"CVE-2023-5177","markdown":"https://insights.sbomify.com/CVE-2023-5177/index.md","name":"CVE-2023-5177","record":{"aliases":["GHSA-fc5f-gc6j-gfhf"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can obtain full file system paths by providing invalid file parameters, potentially aiding further attacks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"vrm360","vendor":"maurice"}],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[],"description":"The Vrm 360 3D Model Viewer WordPress plugin through 1.2.1 exposes the full path of a file when putting in a non-existent file in a parameter of the shortcode.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Vrm 360 3D Model Viewer \u003c= 1.2.1 - Full Path Disclosure","id":"CVE-2023-5177","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Kernel: use after free in nvmet_tcp_free_crypto in nvme","id":"CVE-2023-5178"},"packages":[],"prev":{"headline":"Memory corruption in Firefox","id":"CVE-2023-5176"},"products":["Vrm 360 3D Model Viewer"],"published":"2023-10-16","related":[{"cvss_score":8.8,"headline":"Vrm 360 3D Model Viewer \u003c= 1.2.1 - Contributor+ Arbitrary File Upload Leading to RCE","id":"CVE-2023-4311","kev_date_added":null,"published":"2023-12-18"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["Unknown"]},"summary":"Attackers can obtain full file system paths by providing invalid file parameters, potentially aiding further attacks.","url":"https://insights.sbomify.com/CVE-2023-5177/"}