CVE-2023-49946

Forgejo vulnerability

9.1 CRITICALEPSS 0.86%

Published3 Dec 2023

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.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityNone

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

Forgejo< 1.20.5-1

Remediation

Fixed in

Forgejo≥ 1.20.5-1

Frequently asked

Is CVE-2023-49946 being actively exploited?

CVE-2023-49946 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.86%.

How severe is CVE-2023-49946?

CVE-2023-49946 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.86% probability of exploitation.

Which products are affected by CVE-2023-49946?

Affected products include Forgejo.

How do I fix CVE-2023-49946?

Upgrade affected software to a fixed version, for example Forgejo 1.20.5-1 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2023-49946 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.