How broadly exploitable is this vulnerability?

The issue is broadly exploitable in any deployment where an attacker can obtain or control a Jellyseerr account whose data appears in the Anchorr Jellyseerr user selector, and where an admin subsequently views the affected UI. Once triggered, the stored XSS can be used to steal configuration and escalate to full admin control.

What level of access does an attacker need to exploit this?

The attacker generally needs only standard user-level access to Jellyseerr or another path to inject data into the user selector. They do not need Anchorr admin credentials; the attack relies on the admin's browser rendering the malicious data.

What is the safest general fix pattern for developers?

The most robust fix is to enforce strict output encoding for all user-controlled fields, use secure-by-default templating that escapes values automatically, and redesign configuration endpoints so that secrets are never returned to browser clients. This removes the XSS vector and greatly limits the damage if any UI context is compromised.

Severity:

CRITICAL RISK

(9.0)

Stored Cross-Site Scripting (CWE-80) in Anchorr Jellyseerr User Selector

CVE-2026-32891

Published:

Mar 19, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

Stored Cross-Site Scripting (XSS)

CWE:

CWE-80;CWE-212;CWE-311

Impact:

Account Takeover and Multi-Service Compromise via Stored XSS

Severity:

CRITICAL RISK

(9.0)

CVSS Version:

3.1

Vulnerability Type

Category:

Stored Cross-Site Scripting (XSS)

CWE:

CWE-80;CWE-212;CWE-311

Impact:

Account Takeover and Multi-Service Compromise via Stored XSS

Severity:

CRITICAL RISK

(9.0)

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.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Stored Cross-Site Scripting (CWE-80) in Anchorr Jellyseerr User Selector

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal