dbcve.org
AnchorrApplication · Openvessl

CVE-2026-32891

CRITICAL · 9.0 CVSS v3.1 Published 2026-03-20
Fix available
A fix is available. Upgrade to after 1.4.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable

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
Anchorr is a Discord bot for requesting movies and TV shows and receiving notifications when items are added to a media server. Versions 1.4.1 and below contain a stored XSS vulnerability in the Jellyseerr user selector. Jellyseerr allows any account holder to execute arbitrary JavaScript in the Anchorr admin's browser session. The injected script calls the authenticated /api/config endpoint - which returns the full application configuration in plaintext. This allows the attacker to forge a valid Anchorr session token and gain full admin access to the dashboard with no knowledge of the admin password. The same response also exposes the API keys and tokens for every integrated service, resulting in simultaneous account takeover of the Jellyfin media server (via JELLYFIN_API_KEY), the Jellyseerr request manager (via JELLYSEERR_API_KEY), and the Discord bot (via DISCORD_TOKEN). This issue has been fixed in version 1.4.2.

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

A stored XSS vulnerability in the Jellyseerr user selector of Anchorr Discord bot (versions 1.4.1 and below) allows attackers to inject malicious JavaScript that, when executed by an admin, calls the authenticated /api/config endpoint to exfiltrate the full application configuration including session tokens and API keys for Jellyfin, Jellyseerr, and Discord, enabling full admin account takeover.

MitigationUpgrade Anchorr to version 1.4.2 to patch the stored XSS vulnerability; rotate all exposed API keys and tokens (JELLYFIN_API_KEY, JELLYSEERR_API_KEY, DISCORD_TOKEN) immediately as they may be compromised.

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
AnchorrApplication
Affected:<= 1.4.1

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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Verify Anchorr version
    Check the installed version of Anchorr by inspecting the package.json file, docker image tag, or running the application's version command if available. Compare against the affected range: <= 1.4.1
    Affected if The installed version is 1.4.1 or lower
  2. Confirm Jellyseerr integration is configured
    Examine Anchorr configuration files or environment variables to determine if the Jellyseerr integration feature is enabled. Look for JELLYSEERR related settings in the config file or environment.
    Affected if Jellyseerr integration is enabled and configured in the application
  3. Inspect admin-accessible endpoints for unauthorized access
    Review server access logs or application audit logs for any unexpected or unauthorized POST requests to the /api/config endpoint, especially from IP addresses that are not recognized admin sessions.
    Affected if There are log entries showing /api/config endpoint calls that were not initiated by legitimate administrators
  4. Check for exposed credentials in configuration
    Examine the application configuration (config.json, environment variables, or database) to verify whether sensitive API keys (JELLYFIN_API_KEY, JELLYSEERR_API_KEY, DISCORD_TOKEN) are present and appear to have been accessed or exfiltrated.
    Affected if Any of these API keys or tokens appear in logs, external systems, or show signs of unauthorized access

You are affected if Anchorr version is 1.4.1 or below AND the Jellyseerr integration is enabled, particularly if there is evidence of unauthorized /api/config endpoint access or credential exposure.

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
Upgrade available Upgrade to a release after 1.4.1
Interim mitigation

Upgrade Anchorr to version 1.4.2 to patch the stored XSS vulnerability; rotate all exposed API keys and tokens (JELLYFIN_API_KEY, JELLYSEERR_API_KEY, DISCORD_TOKEN) immediately as they may be compromised.

Recommended fix High confidence

1.4.2

  1. Upgrade Anchorr from version 1.4.1 (or any version <=1.4.1) to version 1.4.2
  2. Restart the Anchorr service to ensure the new version is loaded
  3. Verify the Jellyseerr user selector input is properly sanitized and no longer accepts script tags
  4. Audit the /api/config endpoint response to confirm sensitive tokens are no longer exposed in plaintext

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

Fix this in Anchorr Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32891 — 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-32891 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