GHSA-5m9m-j5p7-m7f9 CVE-2025-61524 GO-2025-4026
Casdoor is vulnerable to Improper Authorization
High
Go
- Severity
- 7.2 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 0.66%
- Chance of exploitation in the next 30 days. Higher than 51.46% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-285 Improper Authorization
- Fix
2.63.0- Upgrade github.com/casdoor/casdoor to this version or later
Description
An issue in the permission verification module and organization/application editing interface in Casdoor before 2.63.0 allows remote authenticated administrators of any organization within the system to bypass the system's permission verification mechanism by directly concatenating URLs after login.
Affected versions
Go
| Package | Vulnerable | Fixed in |
|---|---|---|
| github.com/casdoor/casdoor | < 2.63.0 |
2.63.0 |
| github.com/casdoor/casdoor | all versions |
No fix yet |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
github.com/casdoor/casdoor Go → 2.63.0
- go
go get github.com/casdoor/casdoor@v2.63.0 && go mod tidy
Severity breakdown
CVSS 3.1 7.2
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Weakness
CWE-285: Improper Authorization
The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.
How to prevent it
- Architecture and Design: Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Architecture and Design: Ensure that you perform access control checks related to your business logic. These checks may be different than the access control checks that you apply to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
- Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
- Architecture and Design: For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page. One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
- System Configuration, Installation: Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-mfvp-7p3v-x9mh Casdoor SAML callback handler accepts any well-formed SAMLResponse sent to /api/acs without verifying that it corresponds to an AuthnRequest | Critical | Also affects github.com/casdoor/casdoor |
| GHSA-339w-3hqm-9pjc Casdoor doesn't verify that a JWT used for token exchange is still active | Critical | Also affects github.com/casdoor/casdoor |
| GHSA-rgq2-93gj-ffxg Casdoor doesn't enforce SAML assertion time bounds | High | Also affects github.com/casdoor/casdoor |
| GHSA-c9w5-qp6m-m395 Casdoor: GetTokenExchangeToken bypass through lack of cross-organization JWT signature check | Critical | Also affects github.com/casdoor/casdoor |
| GHSA-3w4h-g9f5-j84p Casdoor does not validate the AudienceRestriction element in SAML assertions | Critical | Also affects github.com/casdoor/casdoor |
| GHSA-gv4m-v8c8-hr3g Casdoor allows users to bypass configured MFA requirements | Medium | Also affects github.com/casdoor/casdoor |
| GHSA-fwgq-j9r9-qjgr Casdoor has an authentication bypass | Critical | Also affects github.com/casdoor/casdoor |
| GHSA-rmxx-v9rj-vpvg Casdoor: Arbitrary file write possible through Local File System storage provider | Medium | Also affects github.com/casdoor/casdoor |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor