# CVE-2025-1447: kasuganosoras Pigeon index.php server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in Pigeon to access internal resources or bypass security controls.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Feb 2025
- **Updated:** 19 Feb 2025
- **Also known as:** GHSA-3gqr-3p72-mqm3

## What is CVE-2025-1447?

CVE-2025-1447 is a medium-severity server-side request forgery vulnerability in kasuganosoras Pigeon, published on 19 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in kasuganosoras Pigeon 1.0.177. It has been declared as critical. This vulnerability affects unknown code of the file /pigeon/imgproxy/index.php. The manipulation of the argument url leads to server-side request forgery. The attack can be initiated remotely. Upgrading to version 1.0.181 is able to address this issue. The patch is identified as 84cea5fe73141689da2e7ec8676d47435bd6423e. It is recommended to upgrade the affected component.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2025-1447 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1447 is a medium-severity server-side request forgery vulnerability in kasuganosoras Pigeon, published on 19 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1447 exists.

Affected product: kasuganosoras Pigeon. 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-1447/ (Markdown: https://insights.sbomify.com/CVE-2025-1447/index.md)
```

## Sources

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

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