CVE-2025-69600
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 · uneditedCommand injection in Raynet rvia RayVentory Scan Engine 12.6 Update 8 and previous versions allows adversaries to execute commands via getconfig, upload, inventory, and oracle options.
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 · high confidenceCommand injection vulnerability in Raynet rvia RayVentory Scan Engine versions 12.6 Update 8 and earlier allows authenticated or unauthenticated adversaries to execute arbitrary operating system commands through the getconfig, upload, inventory, and oracle options. User-supplied input to these functions is not properly sanitized before being passed to system shell execution calls.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 installed RayVentory Scan Engine versionLocate the RayVentory installation directory and check version information in the application metadata, about screen, or version file typically found in the program files folder. Common locations include the main executable or a version info file within the RayVentory installation directory.Affected if The installed version is 12.6 Update 8 or any earlier version within the 12.6 update lineage
-
Verify the web interface or API is accessibleConfirm that the RayVentory service is running and its web interface or API endpoint is reachable on the network. This is typically accessible via HTTP/HTTPS on a configured port.Affected if The service is exposed on the network without proper network segmentation or authentication barriers
-
Check if vulnerable options are enabledExamine the RayVentory configuration settings to determine whether the getconfig, upload, inventory, or oracle functions are enabled and accessible to users. These may be exposed through the web interface, API, or CLI.Affected if Any of these four options (getconfig, upload, inventory, oracle) are enabled and can be accessed without additional security controls
-
Confirm authentication statusReview the authentication configuration for the RayVentory service to determine whether unauthenticated access to the vulnerable functions is possible.Affected if The service allows unauthenticated or weakly authenticated access to the vulnerable functions
A user is affected if their RayVentory Scan Engine installation is version 12.6 Update 8 or earlier AND the vulnerable getconfig, upload, inventory, or oracle options are accessible, regardless of authentication status.
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 dataUpgrade to RayVentory Scan Engine version 12.6 Update 9 or later which patches the command injection vectors. If immediate patching is not feasible, restrict network access to the affected service and disable the vulnerable options until the update can be applied.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69600 — 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-69600 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