# CVE-2025-13084: Opto 22 groov View Exposure of Sensitive Information Through Metadata

> An Editor role user can access the users endpoint to retrieve all user API keys, including those of Administrators, leading to potential account takeover.

- **Severity:** Medium 6.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Nov 2025
- **Updated:** 26 Nov 2025

## What is CVE-2025-13084?

CVE-2025-13084 is a medium-severity vulnerability in Opto 22 GRV-EPIC-PR1 Firmware, published on 26 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The users endpoint in the groov View API returns a list of all users and
 associated metadata including their API keys. This endpoint requires an
 Editor role to access and will display API keys for all users, 
including Administrators.

Weakness: CWE-1230 (Exposure of Sensitive Information Through Metadata)

## Which versions are affected by CVE-2025-13084?


## How do I fix CVE-2025-13084?

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

## Is CVE-2025-13084 being exploited?

There is no known exploitation of CVE-2025-13084 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-13084 and fix it if it is affected.

What it is: CVE-2025-13084 is a medium-severity vulnerability in Opto 22 GRV-EPIC-PR1 Firmware, published on 26 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-13084 in the wild and no public exploit code.

Affected product: Opto 22 GRV-EPIC-PR1 Firmware. 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-2025-13084/ (Markdown: https://insights.sbomify.com/CVE-2025-13084/index.md)
```

## Sources

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

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