CVE-2026-7596: ui-ux-pro-max-skill XSS Vulnerability

CVE-2026-7596 Overview

CVE-2026-7596 is a cross-site scripting (XSS) vulnerability in the nextlevelbuilder/ui-ux-pro-max-skill project, affecting versions up to 2.5.0. The flaw resides in the data.get function within .claude/skills/design-system/scripts/generate-slide.py, part of the Slide Generator component. Attackers can inject script payloads through unsanitized input that the Slide Generator renders. The exploit has been publicly disclosed and remains unpatched. Maintainers were notified through a pull request but have not responded.

Critical Impact

Remote attackers can deliver crafted input that executes arbitrary script in the context of generated slides, enabling content tampering and limited integrity impact on rendered output. User interaction is required.

Affected Products

• nextlevelbuilder ui-ux-pro-max-skill versions up to and including 2.5.0
• Slide Generator component in .claude/skills/design-system/scripts/generate-slide.py
• Downstream projects that consume the unpatched data.get function

Discovery Timeline

• 2026-05-01 - CVE-2026-7596 published to NVD
• 2026-05-05 - Last updated in NVD database

Technical Details for CVE-2026-7596

Vulnerability Analysis

The vulnerability is classified as cross-site scripting [CWE-79]. It originates in the data.get function inside generate-slide.py, which is part of the Slide Generator component. The function reads user-controllable input and incorporates it into generated slide output without applying output encoding or HTML sanitization.

When a victim opens or previews a slide produced from attacker-supplied data, the embedded script executes in the browser context that renders the slide. The attack is reachable over the network and requires user interaction to trigger the rendered payload. According to the public disclosure, the issue was reported to maintainers through a pull request but has not been addressed.

Root Cause

The root cause is missing neutralization of input during web page generation. The data.get call returns attacker-influenced fields that flow into the slide template without escaping characters such as <, >, and ". Any HTML or JavaScript provided in those fields is preserved verbatim in the output document, producing a stored or reflected XSS sink depending on how the generated slide is distributed.

Attack Vector

An attacker submits crafted data — for example, a slide title, body field, or design-system attribute — that contains an HTML <script> element or an event-handler attribute. The Slide Generator pipeline calls data.get to retrieve the field and writes it into the slide markup. When a reviewer or end user opens the generated slide in a browser, the payload executes. Because user interaction is required (opening or previewing the slide), the attacker typically pairs delivery with social engineering or shared review workflows. Refer to the GitHub Pull Request #274 and VulDB Vulnerability #360549 entries for additional technical context.

Detection Methods for CVE-2026-7596

Indicators of Compromise

• Generated slide artifacts containing inline <script> tags, javascript: URIs, or DOM event handlers such as onerror= and onload= in fields produced by generate-slide.py.
• Source data files supplied to the Slide Generator that include HTML control characters in fields normally restricted to plain text.
• Browser console errors or unexpected network beacons originating from previewed slides.

Detection Strategies

• Scan repositories and build outputs for slide artifacts produced by .claude/skills/design-system/scripts/generate-slide.py and grep for HTML or script syntax inside string fields.
• Add a content security policy (CSP) in environments that render generated slides and alert on CSP violation reports.
• Review pull requests and data submissions that modify slide source data for HTML payloads before they reach the generator.

Monitoring Recommendations

• Log all invocations of generate-slide.py along with the input data hashes to support post-incident review.
• Monitor browser telemetry for script execution in pages served from internal slide-hosting domains.
• Track upstream commits on the GitHub Project Repository for a remediation merge.

How to Mitigate CVE-2026-7596

Immediate Actions Required

• Restrict execution of generate-slide.py to trusted input sources until a fix is published.
• Apply HTML escaping to all values returned by data.get before writing them into slide templates.
• Treat any externally contributed slide data as untrusted and review it before generation.

Patch Information

No official patch is available at the time of writing. The maintainers were informed through GitHub Pull Request #274, which proposes a fix, and tracked under GitHub Issue #247. Track the GitHub Project Repository and the VulDB Submission #805510 for status updates.

Workarounds

• Manually apply the changes proposed in the open pull request to your local fork of the project.
• Wrap calls to data.get with a sanitization function such as html.escape before rendering output.
• Serve generated slides with a strict CSP that blocks inline scripts and disallows untrusted origins.
• Limit slide-generation workflows to vetted contributors and reject submissions containing HTML control characters.

# Configuration example: enforce HTML escaping at the generator boundary
# Replace direct data.get() usage in generate-slide.py with an escaped wrapper
import html

def safe_get(data, key, default=""):
    value = data.get(key, default)
    if isinstance(value, str):
        return html.escape(value, quote=True)
    return value