CVE-2026-5468
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 security flaw has been discovered in Casdoor 2.356.0. This affects the function dangerouslySetInnerHTML. Performing a manipulation of the argument formCss/formCssMobile/formSideHtml results in cross site scripting. The attack can be initiated remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceAn XSS vulnerability in Casdoor 2.356.0 allows remote attackers to inject malicious JavaScript via the formCss, formCssMobile, and formSideHtml parameters. These values are rendered using React's dangerouslySetInnerHTML function without sanitization, causing the browser to execute arbitrary script content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.356.0CVSS 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 if Casdoor is deployed in your environmentCheck for running Casdoor processes, web server logs, or container images containing Casdoor. Look for port 8000 or 7001 default ports, or search for casdoor binaries/processes.Affected if Casdoor is installed and accessible in your environment
-
Determine the installed Casdoor versionRun 'casdoor --version' or check the Docker image tag. If running from source, check the version file or git commit. Alternatively, access the /api/get-api-key endpoint or check the login page footer for version info.Affected if The version is exactly 2.356.0
-
Check if application customization settings are accessibleLog into Casdoor as an administrator and navigate to the Application settings or Organization settings page. Look for fields labeled formCss, formCssMobile, or formSideHtml in the customization or theme settings.Affected if You can access and modify these customization parameters in the admin interface
-
Verify if the vulnerable parameters are rendered unsafelyIn the Casdoor web interface, inject a test XSS payload into formCss, formCssMobile, or formSideHtml (e.g., <img src=x onerror=alert(1)>). Save the settings and reload the page to see if the script executes.Affected if The injected JavaScript executes when the page loads, indicating dangerouslySetInnerHTML is in use without sanitization
You are affected if Casdoor version 2.356.0 is running AND you have access to modify application customization parameters that are rendered unsafely via dangerouslySetInnerHTML.
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 dataSanitize all user input to formCss, formCssMobile, and formSideHtml before passing to dangerouslySetInnerHTML, or replace with safe DOM manipulation methods that do not interpret HTML.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5468 — 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-5468 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