Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2026-90931 — Bilingual analysis and safe lab PoC for CVE-2026-90931, a stored XSS in LaraDashboard's SVG media upload, with source verifier, marker payload, and remediation guidance. | Kitploit
Tools/GitHubGitHub/capivara-research/cve-2026-90931
Static AnalysisVulnerability AnalysisWeb Application ExploitationWeb Security
GitHubcapivara-research/cve-2026-90931

CVE-2026-90931

Bilingual analysis and safe lab PoC for CVE-2026-90931, a stored XSS in LaraDashboard's SVG media upload, with source verifier, marker payload, and remediation guidance.

View Repository
Website
518 days agoNot yet reviewed
Share

CVE-2026-90931 — LaraDashboard stored XSS via SVG upload

English | Português do Brasil

CVE NVD GHSA CNA

Public research evidence and safe local-lab reproduction material for stored cross-site scripting in LaraDashboard's media library.

At a glance

FieldValue
ProductLaraDashboard
Official affected range>= 0.9.0, < 1.3.0
Fixed boundary1.3.0
Tested revision9dc1335835701651aef3adcb3e885acecb32402c
WeaknessCWE-79, CWE-434
Official severityCVSS 4.0 5.1 / CVSS 3.1 5.4
Required permissionmedia.create
AdvisoryGHSA-9gxw-qpx8-x9c7
CNA / reporterVulnCheck / capivara-research

The CVE title retains the originally reported 0.9.0 through 1.2.2 wording. The canonical record updated on 2026-10-29 expresses the affected range as >= 0.9.0, < 1.3.0 and marks 1.3.0 unaffected. This repository follows the current structured range and separately preserves the tested revision.

Summary

The production upload pipeline accepts SVG files without sanitizing active content. The files are stored under the application's origin and served inline as image/svg+xml. A content-level user holding only media.create can therefore store JavaScript that executes when another user opens the file.

Root cause

Outside demo mode, MediaUploadRequest applies only generic file and size validation. SVG is explicitly recognized as image/svg+xml, while the subsequent checks validate extension/MIME consistency but never sanitize the SVG DOM or reject scripts and event handlers.

Reproduction

The original coordinated disclosure validated the issue end to end using a custom role with only media.create and media.view.

The poc/ directory contains:

  • a non-invasive source verifier;
  • a harmless SVG marker payload;
  • a loopback-only upload helper requiring explicit --execute.

The marker changes visible text in the SVG document and sets the fragment to XSS_MARKER; it does not read cookies, tokens, or other application data.

For a source-only reproducible check pinned to the audited revision:

docker build -t cve-2026-90931 .
docker run --rm cve-2026-90931

Exit status 1 means vulnerable markers were found; 0 means none were found.

Impact

JavaScript executes in the dashboard origin after user interaction. When opened by an authenticated administrator, same-origin script can act with that user's browser privileges. The published advisory conservatively scores the issue as CVSS 3.1 5.4.

Remediation

  • Sanitize SVG content using a maintained SVG sanitizer.
  • Alternatively reject SVG uploads or force them to download as attachments.
  • Serve user-controlled media from a separate origin.
  • Apply MIME validation in production, not only demo mode.
  • Replace executable-extension blocklists with a strict allowlist.
  • Add Content-Security-Policy and X-Content-Type-Options: nosniff as defense in depth.

Disclosure

Reported through GitHub Private Vulnerability Reporting and published by the project on 2026-08-30. VulnCheck assigned CVE-2026-90931 on 2026-09-14 and credits capivara-research as reporter.

Repository map

.
├── README.md / README.pt-BR.md
├── poc/
│   ├── static_verify.py   # non-invasive source verifier
│   ├── marker.svg         # harmless visible browser marker
│   └── upload_marker.py   # explicit, loopback-only upload helper
├── evidence/official-record-summary.md
├── Dockerfile
├── SECURITY.md
└── LICENSE

Legal and safety notice

Use this material only on systems you own or are explicitly authorized to test. The PoCs are intended for isolated, disposable lab environments.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    871
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    548
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    383
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    361
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    305
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    280

Explore all tools

Browse our collection of tools

View all tools →