CVE-2023-49946

Description

In Forgejo before 1.20.5-1, certain endpoints do not check whether an object belongs to a repository for which permissions are being checked. This allows remote attackers to read private issues, read private pull requests, delete issues, and perform other unauthorized actions.

Category

9.1
CVSS
Severity: Critical
CVSS 3.1 •
EPSS 0.10%
Vendor Advisory codeberg.org Vendor Advisory forgejo.org
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://forgejo.org/2023-11-release-v1-20-5-1/ release notes vendor advisory
https://codeberg.org/forgejo/forgejo/src/branch/forgejo/RELEASE-NOTES.md release notes vendor advisory
https://about.gitea.com/security not applicable
https://github.com/gogs/gogs/security not applicable

Frequently Asked Questions

What is the severity of CVE-2023-49946?
CVE-2023-49946 has been scored as a critical severity vulnerability.
How to fix CVE-2023-49946?
To fix CVE-2023-49946, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2023-49946 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2023-49946 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.