Gitea does not properly validate repository ownership when linking attachments to releases. An attachment uploaded to a private repository could pote…
Gitea does not properly validate ownership when toggling OpenID URI visibility. An authenticated user may be able to change the visibility settings o…
Gitea does not properly validate repository ownership when deleting Git LFS locks. A user with write access to one repository may be able to delete L…
Gitea does not properly validate project ownership in organization project operations. A user with project write access in one organization may be ab…
Gitea does not properly verify repository context when deleting attachments. A user who previously uploaded an attachment to a repository may be able…
Gitea's notification API does not re-validate repository access permissions when returning notification details. After a user's access to a private r…
Gitea's stopwatch API does not re-validate repository access permissions. After a user's access to a private repository is revoked, they may still vi…
In Gitea before 1.25.2, /api/v1/user has different responses for failed authentication depending on whether a username exists.
In Gitea before 1.20.1, a forbidden URL scheme such as javascript: can be used for a link, aka XSS.
Gitea before 1.21.8 inadvertently discloses users' login times by allowing (for example) the lastlogintime explore/users sort order.
Gitea before 1.22.2 sometimes mishandles the propagation of token scope for access control within one of its own package registries.
In Gitea before 1.21.2, an anonymous user can visit a private user's project.
Gitea before 1.22.2 allows XSS because the search input box (for creating tags and branches) is v-html instead of v-text.
Gitea before 1.23.0 allows attackers to add attachments with forbidden file extensions by editing an attachment name via an attachment API.
In Gitea before 1.22.5, branch deletion permissions are not adequately enforced after merging a pull request.
Gitea before 1.22.3 mishandles access to a private resource upon receiving an API token with scope limited to public resources.
Gitea before 1.25.2 mishandles authorization for deletion of releases.
In Gitea through 1.17.1, repo cloning can occur in the migration function.
Gitea before 1.17.3 does not sanitize and escape refs in the git backend. Arguments to git commands are mishandled.
In Gitea before 1.16.9, it was possible for users to add existing issues to projects. Due to improper access controls, an attacker could assign any i…
Cross-site Scripting (XSS) - Stored in GitHub repository go-gitea/gitea prior to 1.16.9.
Gitea before 1.16.7 does not escape git fetch remote.
An arbitrary file deletion vulnerability in Gitea v1.16.3 allows attackers to cause a Denial of Service (DoS) via deleting the configuration file.
Open Redirect on login in GitHub repository go-gitea/gitea prior to 1.16.5.
The avatar middleware in Gitea before 1.13.6 allows Directory Traversal via a crafted URL.
Missing Authorization in GitHub repository go-gitea/gitea prior to 1.16.4.
An Authentication Bypass vulnerability exists in Gitea before 1.5.0, which could let a malicious user gain privileges. If captured, the TOTP code for…
An issue exsits in Gitea through 1.15.7, which could let a malicious user gain privileges due to client side cookies not being deleted and the sessio…
Cross Site Scripting (XSS) vulnerability exists in Gitea before 1.5.1 via the repository settings inside the external wiki/issue tracker URL field.
Gitea before 1.4.3 is affected by URL Redirection to Untrusted Site ('Open Redirect') via internal URLs.