/

CVE-2026-85613

Severity:

HIGH RISK

(8.2)

Cross-Site Scripting (CWE-79) in OpenPanel Favicon Proxy

CVE-2026-85613

Deferred

Vulnerability type

Category:

Cross-Site Scripting

CWE:

CWE-79

Impact:

Same-Origin Script Execution and Credentialed Request Abuse

Severity:

HIGH RISK

(8.2)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

OpenPanel contains a cross-site scripting vulnerability in its unauthenticated favicon proxy endpoint. If the endpoint retrieves an attacker-controlled SVG containing script content, that script may execute in a victim's browser under the API origin and could make authenticated same-origin requests.

Affected context

The issue may affect OpenPanel deployments that expose the unauthenticated GET /misc/favicon endpoint and allow it to retrieve attacker-controlled SVG resources. Risk is increased when the response is served with a browser-interpretable content type and authenticated users access the endpoint or a page that loads its response.

Exploit preconditions

  • Attack surface: The unauthenticated GET /misc/favicon proxy endpoint
  • Required access: No OpenPanel authentication may be required to submit the remote favicon URL; the attacker must be able to host or control the referenced SVG resource
  • Trigger point: A victim's browser requests or renders the proxied SVG response
  • Why exploitation is possible: Active SVG content may be interpreted as script in the API origin, allowing browser requests to reuse the victim's authenticated same-origin context

Why this happens

The vulnerability results from treating remotely sourced SVG content as a passive image without sufficiently constraining its active content or response handling. SVG can contain script-capable elements, and proxying it through an application origin may cause browser-executable content to inherit that origin. This behavior maps to CWE-79: Improper Neutralization of Input During Web Page Generation, because attacker-controlled content can reach a browser execution context without adequate output encoding, sanitization, or isolation.

Potential impact

  • An attacker could execute JavaScript in a victim's browser under the API origin
  • Authenticated same-origin requests could be issued without the victim's explicit intent
  • Account data or other accessible application information may be exposed
  • Application state could be modified through actions available to the victim
  • The vulnerability could support phishing or session-abuse scenarios

General mitigation guidance

Mitigation generally focuses on preventing active, untrusted content from being served in an application origin.

Common defensive patterns include:

  • Restricting favicon retrieval to validated, trusted image formats and sources
  • Sanitizing or rasterizing SVG content before proxying or rendering it
  • Serving untrusted media from an isolated origin with no application credentials
  • Applying restrictive content types and browser security headers
  • Preventing credential-bearing cross-origin requests where they are not required
  • Enforcing authorization and request validation consistently on sensitive endpoints
  • Limiting the proxy's network access and applying least-privilege service permissions

How teams detect issues like this

Organizations commonly detect related risks through:

  • Static analysis for URL fetchers that return untrusted content without type validation or sanitization
  • Code review checks for proxy endpoints that forward attacker-selected resources
  • Testing SVG, HTML, and other active formats across content-type and browser-rendering paths
  • Policy enforcement requiring untrusted media to use an isolated asset origin
  • Security tests verifying that proxied content cannot execute in an authenticated application origin

Automated application security testing and browser-based regression tests can help identify these exposure paths.

Sources

SourceLink
github.comgithub.com/Openpanel-dev/openpanel/security/advisories/GHSA-r7hx-q6f4-vj6h
vulncheck.comvulncheck.com/advisories/openpanel-unauthenticated-xss-via-svg-favicon-proxy

Frequently asked

questions

It may be exploitable remotely because the endpoint is unauthenticated and can retrieve a URL selected by an attacker. Successful impact still depends on a victim's browser requesting or rendering the resulting content.

The described endpoint does not require authentication, so an account may not be necessary. The attacker generally needs control of the SVG resource and a way to induce a victim to access the relevant endpoint or content.

Do not proxy or render untrusted SVG directly from the application origin. Prefer validated, inert image formats, sanitize or rasterize SVGs, and isolate untrusted media on a separate origin.

Treat remote media as untrusted input, enforce strict content-type and source policies, apply browser security headers, and test proxy endpoints for active-content execution and credentialed same-origin behavior.

Find out what's already
exploitable in your codebase.