dbcve.org
CliproxyapiApplication · Router For Me

CVE-2026-8081

MEDIUM · 6.3 CVSS v3.1 Published 2026-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A vulnerability has been found in router-for-me CLIProxyAPI 6.9.29. Affected by this issue is some unknown functionality of the file internal/api/handlers/management/api_tools.go of the component API Interface. The manipulation of the argument url leads to server-side request forgery. Remote exploitation of the attack is possible. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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 confidence

Server-side request forgery (SSRF) vulnerability in router-for-me CLIProxyAPI 6.9.29 within the API Interface component (internal/api/handlers/management/api_tools.go). The url parameter is not properly validated, allowing an attacker to manipulate the server into making arbitrary HTTP requests to internal or external resources.

MitigationImplement strict allowlist-based URL validation and input sanitization for the url parameter. Consider network segmentation to limit the impact of SSRF and restrict outbound connections from the server.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CliproxyapiApplication
Affected:= 6.9.29

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed version of Router For Me Cliproxyapi
    Run the CLI tool with version flag (e.g., router-for-me cliproxyapi --version or -v) or check the binary/application metadata
    Affected if The installed version is exactly 6.9.29
  2. Confirm the API Interface component is accessible
    Attempt to access the internal API endpoint at internal/api/handlers/management/api_tools.go or verify the management API service is running and reachable
    Affected if The API Interface component is enabled and responds to requests
  3. Verify the management API endpoint accepts a url parameter
    Send a test request to the relevant API endpoint with a url parameter (e.g., GET /api/management/tools?url=http://example.com) and observe if the server processes it
    Affected if The url parameter is accepted without strict validation or allowlist filtering
  4. Check if outbound HTTP requests can be triggered
    Send a request with an internal URL (e.g., http://localhost, http://127.0.0.1) or an external URL as the url parameter value and verify if the server makes the request
    Affected if The server successfully makes HTTP requests to arbitrary URLs provided in the url parameter

You are affected if Router For Me Cliproxyapi version 6.9.29 is installed and the API Interface management endpoint is enabled, allowing arbitrary URL manipulation through the unvalidated url parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict allowlist-based URL validation and input sanitization for the url parameter. Consider network segmentation to limit the impact of SSRF and restrict outbound connections from the server.

Recommended fix Low confidence
  1. No vendor-provided fix or patch information is available in the referenced sources.
  2. The vendor was contacted but did not respond to the disclosure.
  3. Consider reaching out to the vendor directly for status updates on a potential fix.
  4. If possible, review the code in internal/api/handlers/management/api_tools.go to implement input validation on the url parameter to mitigate SSRF.
  5. Implement allowlist-based validation for the url parameter to restrict requests to trusted domains/IPs.
  6. Apply network segmentation to limit the impact of potential SSRF exploitation.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cliproxyapi Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8081 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8081 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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