CVE-2025-13087
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability exists in the Opto22 Groov Manage REST API on GRV-EPIC and groov RIO Products that allows remote code execution with root privileges. When a POST request is executed against the vulnerable endpoint, the application reads certain header details and unsafely uses these values to build commands, allowing an attacker with administrative privileges to inject arbitrary commands that execute as root.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Groov Manage REST API on GRV-EPIC and groov RIO products contains a command injection vulnerability where HTTP header values from POST requests are unsafely incorporated into shell commands without proper sanitization. An attacker with administrative credentials can inject arbitrary shell commands that execute with root privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the device or its management interface and verify the model is either GRV-EPIC or groov RIO. This information is typically displayed on the device web interface login page or in the system information section.Affected if The device is a GRV-EPIC or groov RIO unit.
-
Check the firmware versionLog into the Groov Manage interface and navigate to System > System Information or similar. Locate the firmware version displayed there.Affected if The firmware version has not been patched to include the vendor fix for command injection in header handling.
-
Verify REST API accessibilityAttempt to access the Groov Manage REST API endpoint (typically https://<device-ip>/api) using a web browser or curl command. Confirm the API is reachable over the network.Affected if The REST API is exposed to network segments accessible to potential attackers.
-
Confirm administrative credentials are in useCheck the user accounts configured in the Groov Manage interface under Users or Access Control. Verify if any administrative accounts exist.Affected if Administrative credentials are configured, as the vulnerability requires administrative-level access to exploit.
-
Audit for unauthorized access or unusual activityReview system logs in the Groov Manage interface for any unexpected API calls, especially those with unusual header values, or commands that appear to be injection attempts. Check for new or unfamiliar user accounts.Affected if Logs show suspicious API requests with abnormal header content or unexpected administrative actions.
The environment is affected if the device is a GRV-EPIC or groov RIO with a firmware version prior to the vendor patch, where the REST API is network-accessible and administrative credentials exist.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict administrative access to trusted personnel only, implement network segmentation to limit exposure, and apply vendor-supplied patches when available. Consider additional authentication layers for administrative interfaces.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13087 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-13087 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data