# CVE-2025-47244: Auth bypass in ProGet

> Remote attackers can bypass authentication via C# reflection to cause denial of service or access sensitive information if anonymous access is enabled or via CSRF.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 May 2025
- **Updated:** 5 May 2025
- **Also known as:** GHSA-9vqf-p3v5-qmh2

## What is CVE-2025-47244?

CVE-2025-47244 is a high-severity authentication bypass vulnerability in Inedo ProGet, published on 3 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Inedo ProGet through 2024.22 allows remote attackers to reach restricted functionality through the C# reflection layer, as demonstrated by causing a denial of service (when an attacker executes a loop calling RestartWeb) or obtaining potentially sensitive information. Exploitation can occur if Anonymous access is enabled, or if there is a successful CSRF attack.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2025-47244?


## How do I fix CVE-2025-47244?

No fix has been published for CVE-2025-47244 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-47244 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-47244 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-47244 and fix it if it is affected.

What it is: CVE-2025-47244 is a high-severity authentication bypass vulnerability in Inedo ProGet, published on 3 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-47244 exists.

Affected product: Inedo ProGet. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-47244/ (Markdown: https://insights.sbomify.com/CVE-2025-47244/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-47244
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-47244
- OSV: https://osv.dev/vulnerability/CVE-2025-47244

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-47244/
Summaries are generated and may contain mistakes; the official description above is the record.