Gitea versions up to and including 1.26.1 do not apply public-only token filtering consistently to the user organization API, leaving an incomplete fix for CVE-2025-68941.

Affected: Go: code.gitea.io/gitea

## Summary

Two related issues in the token public-only scope enforcement introduced by PR #32204 (CVE-2025-68941 fix). A public-only scoped API token can access private organization data.

## Issue 1: /user/orgs missing checkTokenPublicOnly()

`routers/api/v1/api.go` line 1599: ```go m.Get("/user/orgs", reqToken(), tokenRequiresScopes( auth_model.AccessTokenScopeCategoryUser, auth_model.AccessTokenScopeCategoryOrganization, ), org.ListMyOrgs) // Missing checkTokenPublicOnly() ```

Adjacent route at line 1603 has it: ```go m.Group("/users/{username}/orgs", func() { ... }, ..., checkTokenPublicOnly()) ```

## Issue 2: checkTokenPublicOnly switch-case evaluates only first matching category

`routers/api/v1/api.go` lines 253-295. Go switch executes only the first matching case. For routes with categories [User, Organization]:

1. Organization case matches first (line 263) 2. ctx.Org.Organization is nil on user routes, passes 3. ctx.ContextUser.IsOrganization() is false, passes 4. User case (line 273) is never reached 5. User visibility check skipped entirely

## Steps to Reproduce

1. Create a token with public-only scope (Settings > Applications > check "public only") 2. Call: `curl -H "Authorization: token <PUBLIC_ONLY_TOKEN>" https://gitea.example.com/api/v1/user/orgs` 3. Response includes private and limited-visibility organizations

Expected: only public organizations returned.

## Impact

Public-only scoped tokens can enumerate private organizations the token…

Ein Angreifer kann mehrere Schwachstellen in Gitea ausnutzen, um möglicherweise erweiterte Privilegien zu erlangen, Sicherheitsmaßnahmen zu umgehen oder Daten zu manipulieren und offenzulegen.