CVE-2026-36728
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 · uneditedA markdown based cross-site scripting (XSS) vulnerability in the AI assistant chat function of FastapiAdmin v2.2.0 allows attackers to execute arbitrary web scripts or HTML via injecting a crafted payload into a chat message.
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 confidenceFastapiAdmin v2.2.0 contains a stored cross-site scripting (XSS) vulnerability in its AI assistant chat function. The application fails to properly sanitize markdown content submitted in chat messages, allowing attackers to inject malicious HTML or JavaScript payloads that execute when other users view the chat. This is a classic markdown parsing vulnerability where unsafe HTML within markdown is rendered without sanitization.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed FastapiAdmin versionCheck the installed package version using pip show fastapi-admin or check your requirements.txt / pyproject.toml for the fastapi-admin version entryAffected if Version is 2.2.0 or falls within the affected range without the patch applied
-
Verify AI assistant chat feature is enabledLocate your FastapiAdmin configuration files (typically admin_config.py or similar) and check if the AI assistant module is registered and accessible in your URL routingAffected if The AI assistant chat endpoint (typically /admin/ai-chat or similar path) is active and reachable in your application
-
Confirm markdown is being rendered in chat responsesExamine the FastapiAdmin source code or template files responsible for the AI chat interface; look for how chat message content is handled and whether a markdown renderer is invoked without sanitizationAffected if User-supplied content is passed directly to a markdown parser without HTML sanitization or encoding before being rendered in the browser
-
Test for XSS via crafted markdown payloadSend a test message to the AI assistant chat containing a simple XSS probe such as [script](javascript:alert(1)) or <img src=x onerror=alert(1)> and observe whether the browser executes the script when the response is displayedAffected if The malicious payload renders as executable HTML/Script in the browser rather than being escaped or stripped
You are affected if FastapiAdmin version 2.2.0 is in use, the AI assistant chat feature is enabled, and markdown content from chat messages is rendered without proper sanitization allowing injected scripts to execute.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement server-side sanitization of markdown content using a safe markdown parser (e.g., bleach, dompurify) that strips dangerous HTML/script elements before rendering. Additionally, apply output encoding when displaying chat messages to prevent script execution.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36728 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-36728 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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