# CVE-2025-63716: Cross-site request forgery in n/a

> Attackers can perform unauthorized state-changing operations in the Leads Manager Tool due to missing CSRF protection mechanisms.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Nov 2025
- **Updated:** 12 Nov 2025
- **Also known as:** GHSA-rhj9-2v59-8ccx

## What is CVE-2025-63716?

CVE-2025-63716 is a medium-severity vulnerability in n/a, published on 7 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The SourceCodester Leads Manager Tool v1.0 is vulnerable to Cross-Site Request Forgery (CSRF) attacks that allow unauthorized state-changing operations. The application lacks CSRF protection mechanisms such as anti-CSRF tokens or same-origin verification for critical endpoints.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Rems Leads Manager Tool.

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

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

## Is CVE-2025-63716 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-7942](https://insights.sbomify.com/CVE-2024-7942/): SourceCodester Leads Manager Tool update-leads.php cross site scripting (medium 5.3)
- [CVE-2024-7643](https://insights.sbomify.com/CVE-2024-7643/): SourceCodester Leads Manager Tool Delete Leads delete-leads.php sql injection (medium 5.3)
- [CVE-2024-7644](https://insights.sbomify.com/CVE-2024-7644/): SourceCodester Leads Manager Tool Add Leads add-leads.php cross site scripting (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63716 is a medium-severity vulnerability in n/a, published on 7 Nov 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-63716 exists.

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

## Sources

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

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