dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-50883

CRITICAL · 9.6 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

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
An HTML injection vulnerability in the /src/highlight.rs component of matze wastebin v3.4.1 allows attackers to execute arbitrary scripts via a crafted payload.

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 · moderate confidence

A cross-site scripting (XSS) vulnerability in the highlight.rs component of pastebin application wastebin v3.4.1 allows attackers to inject arbitrary JavaScript via unsanitized HTML in crafted payloads, potentially leading to session hijacking or malicious actions against other users.

MitigationImplement proper HTML sanitization and output encoding in the highlight.rs component to neutralize script execution, and upgrade to any patched version if available.

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify if wastebin is deployed
    Check for running processes or installed packages named 'wastebin', or look for the wastebin binary/web service in common locations (/usr/bin/wastebin, /opt/wastebin, or running as a container)
    Affected if wastebin pastebin application is present in the environment
  2. Determine installed version
    Run 'wastebin --version' or check the version displayed on the web interface, or inspect the binary/package version metadata
    Affected if version is 3.4.1 or falls within the v3.4.x range prior to any available patch
  3. Verify highlight.rs component is accessible
    Attempt to access the highlight functionality - typically at an endpoint like /highlight, /code/highlight, or similar URL path that invokes the highlight.rs component for syntax highlighting
    Affected if the highlight endpoint is reachable without authentication or accessible to users
  4. Test for XSS in highlight component
    Submit a test payload containing unsanitized HTML (e.g., <script>alert('XSS')</script>) via the highlight feature and observe if the script executes in the response
    Affected if the submitted HTML is reflected unmodified in the output and the script executes in a browser context

User is affected if wastebin version 3.4.1 is running and the highlight.rs component is accessible, allowing injected HTML/JS to execute without sanitization.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper HTML sanitization and output encoding in the highlight.rs component to neutralize script execution, and upgrade to any patched version if available.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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