/

CVE-2026-75933

Severity:

HIGH RISK

(7.3)

Stored XSS (CWE-79) in Jet Admin Sign-In Script Options

CVE-2026-75933

Awaiting Analysis

Vulnerability type

Category:

Cross-Site Scripting

CWE:

CWE-79

Impact:

Arbitrary JavaScript Execution

Severity:

HIGH RISK

(7.3)

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

Jet Admin contains a cross-site scripting vulnerability in the sign-in page's scripts and styles configuration option. An authenticated attacker may inject JavaScript that executes in the browser context of users who visit the affected domain.

Affected context

The vulnerability occurs in Jet Admin deployments where an authenticated user can configure scripts or styles associated with the sign-in page. It becomes risky when those values are stored or rendered without sufficient output encoding or sanitization and are subsequently delivered to other users' browsers.

Exploit preconditions

  • Attack surface: Jet Admin sign-in page configuration
  • Required access: An authenticated account with permission to modify scripts or styles options
  • Trigger point: A user's browser loads the affected sign-in page
  • Why exploitation is possible: Attacker-controlled content is rendered as active page content without adequate context-aware output encoding or sanitization

Why this happens

The underlying issue is improper neutralization of user-controlled input in web page output, mapping to CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'). The scripts and styles configuration accepts content that can be interpreted by the browser as executable markup or script rather than treating it strictly as inert configuration data.

Potential impact

  • An attacker may execute JavaScript in visiting users' browser sessions
  • Sensitive page content or accessible tokens could be exposed
  • User actions could be performed within the victim's authorized session
  • The sign-in experience could be altered or used for phishing
  • Administrative users or other visitors could be targeted

General mitigation guidance

Mitigation generally focuses on reducing trust in configurable page content and ensuring that data is treated according to its intended context.

Common defensive patterns include:

  • Apply context-aware output encoding before rendering configurable values
  • Sanitize HTML and script-related input using narrowly defined allowlists where such content is required
  • Prefer declarative, non-executable configuration over arbitrary script injection
  • Restrict script and style configuration to trusted administrators with least privilege
  • Use a restrictive Content Security Policy as defense in depth
  • Separate administrative configuration capabilities from ordinary authenticated access

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis rules identifying unsanitized values inserted into HTML, script, or style contexts
  • Code review checks for configuration fields rendered directly into sign-in pages
  • Tests that verify special characters and markup are encoded in every output context
  • Monitoring for unexpected changes to sign-in page scripts and styles
  • Policy enforcement requiring security review for features that render administrator-controlled content

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

Sources

SourceLink
raw.githubusercontent.comraw.githubusercontent.com/cisagov/CSAF/develop/csaf_files/IT/white/2026/va-26-232-02.json
cve.orgcve.org/CVERecord?id=CVE-2026-75933
jetadmin.iojetadmin.io/

Frequently asked

questions

It may be exploitable through the Jet Admin web interface when an authenticated user can modify the sign-in page scripts or styles configuration and other users subsequently visit that page.

Yes, the described attack requires an authenticated account with sufficient permission to change the affected configuration. Victims generally only need to visit the impacted sign-in page.

Treat configuration values as untrusted, avoid arbitrary executable content where possible, and apply context-aware output encoding or narrowly scoped sanitization before rendering.

Use least-privilege configuration roles, review dynamic page-rendering features, enforce restrictive browser security policies, and test all user-controlled values across HTML, script, and style contexts.

Find out what's already
exploitable in your codebase.