CVE-2026-36725
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 /system/notice/create endpoint of FastapiAdmin v2.2.0 allows attackers to execute arbitrary web scripts or HTML via injecting a crafted payload into the notice_content parameter.
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 confidenceA stored XSS vulnerability exists in FastapiAdmin v2.2.0 where the /system/notice/create endpoint accepts markdown content through the notice_content parameter without proper sanitization. When the notice is rendered, malicious payloads embedded in markdown syntax are executed in the victim's browser.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 versionRun 'pip show fastapi-admin' or check your project's dependency lock file to determine the installed version of FastapiAdminAffected if The installed version is 2.2.0 or falls within any affected version range that includes this release
-
Verify notice module is enabledCheck your FastapiAdmin configuration files (typically in your project settings or admin configuration) to confirm the notice/system module is loaded and accessibleAffected if The notice module is enabled and the /system/notice/create endpoint is reachable
-
Confirm notice creation feature is accessibleAttempt to access the /system/notice/create endpoint via your web application or check router configurations for the notice creation routeAffected if The endpoint exists and accepts user input for the notice_content parameter
-
Test markdown rendering behaviorCreate a test notice with markdown content containing potential XSS payloads (e.g., <script>alert(1)</script> or <img src=x onerror=alert(1)>) and then view the notice as another user would see itAffected if The submitted markdown content is rendered in the notice view without server-side sanitization, allowing the injected HTML/script to execute in another user's browser
You are affected if FastapiAdmin version 2.2.0 (or an affected version) is installed, the notice module is enabled, and the notice_content parameter accepts and renders markdown input without sanitization when other users view the notice.
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 output sanitization for markdown content using a proper HTML sanitization library (e.g., bleach, DOMPurify) to strip dangerous HTML/script tags before rendering, and apply context-aware output encoding.
- 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-36725 — 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-36725 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