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

> An attacker can trick an authenticated admin into deleting user accounts via a malicious page due to missing CSRF protections.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Nov 2025
- **Updated:** 10 Nov 2025
- **Also known as:** GHSA-qm2h-8p28-f32f

## What is CVE-2025-63711?

CVE-2025-63711 is a high-severity vulnerability in n/a, published on 10 Nov 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A Cross-Site Request Forgery (CSRF) vulnerability in the SourceCodester Client Database Management System 1.0 allows an attacker to cause an authenticated administrative user to perform user deletion actions without their consent. The application's user deletion endpoint (e.g., superadmin_user_delete.php) accepts POST requests containing a user_id parameter and does not enforce request origin or anti-CSRF tokens. Because the endpoint lacks proper authentication/authorization checks and CSRF protections, a remote attacker can craft a malicious page that triggers deletion when visited by an authenticated admin, resulting in arbitrary removal of user accounts.

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

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

It affects 1 product.


Products: Lerouxyxchire Client Database Management System.

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

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

## Is CVE-2025-63711 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-46188](https://insights.sbomify.com/CVE-2025-46188/): SQL injection in n/a (critical 9.8)
- [CVE-2025-46189](https://insights.sbomify.com/CVE-2025-46189/): SQL injection in n/a (critical 9.8)
- [CVE-2025-46190](https://insights.sbomify.com/CVE-2025-46190/): SQL injection in n/a (critical 9.8)
- [CVE-2025-46191](https://insights.sbomify.com/CVE-2025-46191/): File upload in n/a (critical 9.8)
- [CVE-2025-46192](https://insights.sbomify.com/CVE-2025-46192/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63711 is a high-severity vulnerability in n/a, published on 10 Nov 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63711 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-63711/ (Markdown: https://insights.sbomify.com/CVE-2025-63711/index.md)
```

## Sources

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

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