# CVE-2025-10410: SourceCodester Link Status Checker index.php server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in the Link Status Checker application via the proxy argument.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 14 Sep 2025
- **Updated:** 15 Sep 2025
- **Also known as:** GHSA-8f96-5hjm-cvqf

## What is CVE-2025-10410?

CVE-2025-10410 is a medium-severity server-side request forgery vulnerability in SourceCodester Link Status Checker, published on 14 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security vulnerability has been detected in SourceCodester Link Status Checker 1.0. This vulnerability affects unknown code of the file index.php. The manipulation of the argument proxy leads to server-side request forgery. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used.

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

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

It affects 1 product.


Products: Rems Link Status Checker.

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

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

## Is CVE-2025-10410 being exploited?

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

## Other vulnerabilities in SourceCodester Link Status Checker

- [CVE-2025-60313](https://insights.sbomify.com/CVE-2025-60313/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10410 is a medium-severity server-side request forgery vulnerability in SourceCodester Link Status Checker, published on 14 Sep 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-10410 exists.

Affected product: SourceCodester Link Status Checker. 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-10410/ (Markdown: https://insights.sbomify.com/CVE-2025-10410/index.md)
```

## Sources

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

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