# CVE-2023-5177: Vrm 360 3D Model Viewer <= 1.2.1 - Full Path Disclosure

> Attackers can obtain full file system paths by providing invalid file parameters, potentially aiding further attacks.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2023
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-fc5f-gc6j-gfhf

## What is CVE-2023-5177?

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.

### Official 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.

## Which versions are affected by CVE-2023-5177?

It affects 1 product.


Products: Maurice Vrm360.

## How do I fix CVE-2023-5177?

No fix has been published for CVE-2023-5177 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-5177 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5177 exists.

## Other vulnerabilities in Unknown Vrm 360 3D Model Viewer

- [CVE-2023-4311](https://insights.sbomify.com/CVE-2023-4311/): Vrm 360 3D Model Viewer <= 1.2.1 - Contributor+ Arbitrary File Upload Leading to RCE (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-5177 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5177 exists.

Affected product: Unknown Vrm 360 3D Model Viewer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-5177/ (Markdown: https://insights.sbomify.com/CVE-2023-5177/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-5177
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-5177
- OSV: https://osv.dev/vulnerability/CVE-2023-5177

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-5177/
Summaries are generated and may contain mistakes; the official description above is the record.