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

> An attacker can trick authenticated users into sending arbitrary chat messages via a forged request due to missing CSRF protections.

- **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:** 10 Nov 2025
- **Updated:** 12 Nov 2025
- **Also known as:** GHSA-xmvm-rgp2-5wfw

## What is CVE-2025-63710?

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

### Official description

The send_message.php endpoint in SourceCodester Simple Public Chat Room 1.0 is vulnerable to Cross-Site Request Forgery (CSRF). The application does not implement any CSRF-protection mechanisms such as tokens, nonces, or same-site cookie restrictions. An attacker can create a malicious HTML page that, when visited by an authenticated user, will automatically submit a forged POST request to the vulnerable endpoint. This request will be executed with the victim's privileges, allowing the attacker to perform unauthorized actions on their behalf, such as sending arbitrary messages in any chat room.

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

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

It affects 1 product.


Products: Pijey Simple Public Chat Room.

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

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

## Is CVE-2025-63710 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63710 is a medium-severity vulnerability in n/a, published on 10 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-63710 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-63710/ (Markdown: https://insights.sbomify.com/CVE-2025-63710/index.md)
```

## Sources

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

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