/

CVE-2026-90943

Severity:

HIGH RISK

(8.7)

Stored XSS (CWE-79) in Filament Comments Extension

CVE-2026-90943

Deferred

Vulnerability type

Category:

Stored Cross-Site Scripting

CWE:

CWE-79

Impact:

Client-Side Code Execution and Account Compromise

Severity:

HIGH RISK

(8.7)

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

A stored cross-site scripting vulnerability in parallax filament-comments through version 3.0.0 allows authenticated panel users to save malicious script content in comment bodies. When other users, including administrators, view the affected comments, the script may execute in their browsers and enable session theft or unauthorized actions.

Affected context

The vulnerability occurs in deployments using the parallax filament-comments extension where comment body content is rendered without sufficient output encoding or sanitization. It becomes risky when authenticated panel users can create or modify comments and other privileged users can view those comments in a browser context with access to sensitive application functionality.

Exploit preconditions

  • Attack surface: Authenticated administrative or application panel comment functionality
  • Required access: An authenticated account permitted to submit or edit comments
  • Trigger point: Rendering a stored comment body in another user's browser
  • Why exploitation is possible: User-controlled comment content is incorporated into an HTML response without adequate context-aware output encoding or sanitization

Why this happens

The underlying bug is an output-neutralization failure in comment rendering. Untrusted comment data is treated as safe markup or script-capable content instead of being encoded for its output context before insertion into the page. This behavior maps to CWE-79: Improper Neutralization of Input During Web Page Generation, commonly known as cross-site scripting.

Potential impact

  • An attacker may execute script in the browser sessions of users viewing affected comments
  • Session identifiers or other sensitive browser-accessible data could be exposed
  • Administrative actions may be performed without the victim's intentional approval
  • Account settings, content, or permissions could be altered
  • The vulnerability could support further compromise of application data or workflows

General mitigation guidance

Mitigation generally focuses on treating all comment content as untrusted and applying context-aware output encoding at render time.

Common defensive patterns include:

  • Encoding comment content according to its HTML, attribute, or JavaScript output context
  • Allowing rich text only through a narrowly defined, security-reviewed sanitization policy
  • Using templating mechanisms that escape output by default
  • Separating trusted administrative markup from user-controlled comment data
  • Limiting panel permissions so comment authors have only the access necessary for their role
  • Applying appropriate session protections and reducing the privileges of administrative browser sessions

How teams detect issues like this

Organizations can look for stored XSS risks through:

  • Static analysis rules identifying unescaped comment or user-content variables in templates
  • Code review checks for raw HTML rendering, unsafe template directives, and custom sanitizers
  • Dynamic testing that submits benign encoding and markup test cases through comment fields
  • Content-security and web application policies that detect or constrain unexpected script execution
  • Audit logging for comment creation, modification, and unusual administrative actions

Automated application security and code review tools may help identify unsafe rendering patterns, but findings should be validated against the actual output context.

Sources

SourceLink
github.comgithub.com/parallax/filament-comments/blob/3.0.0/resources/views/comments.blade.php
github.comgithub.com/parallax/filament-comments/blob/3.0.0/src/Policies/FilamentCommentPolicy.php
hackindex.iohackindex.io/research/stored-xss-filament-comments-unescaped-rendering
packagist.orgpackagist.org/packages/parallax/filament-comments
vulncheck.comvulncheck.com/advisories/parallax-filament-comments-through-3.0.0-stored-xss-via-comment-body

Frequently asked

questions

It can be exploited through the application's panel if an attacker has authenticated access that permits creating or editing comments. The stored payload executes when another user views the affected content.

Not necessarily. The key requirement is permission to submit content that is later rendered to other users. Impact may be greater when an administrator or another privileged user views the comment.

Treat comment bodies as untrusted data, escape them by default for their rendering context, and apply a narrowly scoped sanitizer only when approved rich-text features are required.

Combine secure-by-default templating, output-encoding reviews, focused security testing of user-generated content, restrictive panel permissions, and browser-side security policies such as an appropriate Content Security Policy.

Find out what's already
exploitable in your codebase.