# CVE-2025-62797: CSRF in FluxCP account endpoints allows account takeover / state-changing actions

> Attackers can trick logged-in users into performing unauthorized actions on FluxCP, leading to account takeover or data modification.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **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:** 29 Oct 2025
- **Updated:** 29 Oct 2025
- **Also known as:** GHSA-5w2g-8cqq-r4fr

## What is CVE-2025-62797?

CVE-2025-62797 is a high-severity vulnerability in rathena FluxCP, published on 29 Oct 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

FluxCP is a web-based Control Panel for rAthena servers written in PHP. A critical Cross-Site Request Forgery (CSRF) vulnerability exists in the FluxCP-based website template used by multiple rAthena/Ragnarok servers. State-changing POST endpoints accept browser-initiated requests that are authorized solely by the session cookie without per-request anti-CSRF tokens or robust Origin/Referer validation. An attacker who can lure a logged-in user to an attacker-controlled page can cause that user to perform sensitive actions without their intent. This vulnerability is fixed with commit e3f130c.

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

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


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

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

## Is CVE-2025-62797 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-62797 is a high-severity vulnerability in rathena FluxCP, published on 29 Oct 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-62797 exists.

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

## Sources

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

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