CVE-2026-5469
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 weakness has been identified in Casdoor 2.356.0. This vulnerability affects unknown code of the component Webhook URL Handler. Executing a manipulation can lead to server-side request forgery. The attack can be launched remotely. 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 confidenceCasdoor 2.356.0 contains a server-side request forgery (SSRF) vulnerability in the Webhook URL Handler component. Attackers can manipulate webhook URL inputs to make the server perform requests to arbitrary internal or external resources, potentially accessing internal services, cloud metadata endpoints, or internal network infrastructure.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 Casdoor installation versionCheck the running Casdoor instance version by querying the /api/version endpoint, reviewing docker container labels, or inspecting the binary/build metadataAffected if The installed version is exactly 2.356.0
-
Locate webhook configuration storageExamine Casdoor's configuration for webhook definitions - typically stored in the database (often under a webhooks table) or in the conf/app.conf file if file-based config is usedAffected if Webhook configurations exist in the system
-
Verify webhook URL handling is exposedReview if the webhook API endpoints (typically /api/webhook/*) are accessible and check whether any webhooks have been created with configurable URL fieldsAffected if Webhooks exist with user-settable URL parameters and the API is accessible
-
Inspect URL validation logicSearch the Casdoor source code or configuration for any URL allowlisting, domain whitelist, or internal IP blocking rules applied to webhook URLsAffected if No URL allowlisting or whitelist validation is configured for webhook URLs
-
Check network exposureReview firewall rules, network policies, or cloud security groups to determine if the Casdoor server can reach internal services (internal IPs, localhost, cloud metadata endpoints)Affected if The server has network access to internal resources without additional filtering
You are affected if running Casdoor version 2.356.0 with webhooks enabled and no URL allowlisting or internal network blocking is configured for webhook URL handling.
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 strict URL validation allowing only whitelisted domains or protocols for webhook URLs. Consider network segmentation to prevent the application server from accessing internal resources. Disable or restrict webhook functionality until a vendor patch is available.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5469 — 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-5469 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