CVE-2023-49946
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a broken access control vulnerability in Forgejo where certain API endpoints fail to validate that requested objects (issues, pull requests) belong to the repository for which permission checks are being performed. Attackers can exploit this to read private issues and pull requests, delete issues, and perform other unauthorized cross-repository actions without proper authorization.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.20.5-1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed Forgejo versionLog into the Forgejo admin panel and navigate to the Site Administration > System Info page, or run 'git --git-dir=/path/to/git/repo log -1 --format=%s' from the Forgejo installation directory to check the versionAffected if The installed version is earlier than 1.20.5-1
-
Verify API access is enabledCheck the Forgejo configuration file (custom/conf/app.ini) for the [api] section and verify ENABLE_SWAGGER is set to true, or attempt a GET request to /api/v1/versionAffected if The API is enabled and accessible to users
-
Confirm multi-repository environmentIn the Forgejo admin panel, check the total number of repositories and users. Cross-repository access requires at least two repositories with different owners accessible to the same userAffected if There are multiple repositories with different ownership accessible to authenticated users
-
Check for sensitive issues and pull requestsReview repository settings to identify any private issues or pull requests that contain sensitive informationAffected if Private issues or pull requests exist in repositories where unauthorized cross-repo access could expose them
You are affected if your Forgejo version is earlier than 1.20.5-1, the API is enabled, and you have multiple repositories where users could potentially access objects from repositories they do not own.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.20.5-1
Upgrade to Forgejo version 1.20.5-1 or later which implements proper repository ownership validation for all affected endpoints.
1.20.5-1
- Backup your Forgejo installation and data before upgrading
- Stop the Forgejo service
- Upgrade Forgejo to version 1.20.5-1 or later
- Verify the upgrade was successful by checking the version number
- Restart the Forgejo service
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-49946 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-49946 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data