# CVE-2025-34410: 1Panel CSRF in Change Username Functionality Allows Account Lockout

> Attackers can force authenticated users to change their username via CSRF, causing account lockout and denial of service.

- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:H/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:** Yes
- **Published:** 10 Dec 2025
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-rpr2-4hqj-hc4q, GO-2025-4229

## What is CVE-2025-34410?

CVE-2025-34410 is a high-severity vulnerability in LXware 1Panel, published on 10 Dec 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

1Panel versions 1.10.33 - 2.0.15 contain a cross-site request forgery (CSRF) vulnerability in the Change Username functionality available from the settings panel (/settings/panel). The endpoint does not implement CSRF protections such as anti-CSRF tokens or Origin/Referer validation. An attacker can craft a malicious webpage that submits a username-change request; when a victim visits the page while authenticated, the browser includes valid session cookies and the request succeeds. This allows an attacker to change the victim’s 1Panel username without consent. After the change, the victim is logged out and unable to log in with the previous username, resulting in account lockout and denial of service.

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

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

3 open source packages ship an affected version, including github.com/1Panel-dev/1Panel. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/1Panel-dev/1Panel` | Go | All versions | None |
| `github.com/1Panel-dev/1Panel` | Go | From 1.10.33 to 2.0.15 | None |
| `github.com/1Panel-dev/1Panel` | Go | From 1.10.33 to 2.0.15 | None |

Products: Fit2cloud 1panel.

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

Upgrade to a fixed version.

## Is CVE-2025-34410 being exploited?

There is no known exploitation of CVE-2025-34410 in the wild and no public exploit code.

## Other vulnerabilities in LXware 1Panel

- [CVE-2024-39911](https://insights.sbomify.com/CVE-2024-39911/): 1Panel SQL injection (critical 10.0)
- [CVE-2024-39907](https://insights.sbomify.com/CVE-2024-39907/): a sqlinjection in 1Panel (critical 9.8)
- [CVE-2025-56413](https://insights.sbomify.com/CVE-2025-56413/): Command injection in n/a (high 8.8)
- [CVE-2025-54424](https://insights.sbomify.com/CVE-2025-54424/): 1Panel Agent Bypasses Certificate Verification Leading to Arbitrary Command Execution (high 8.1)
- [CVE-2025-66507](https://insights.sbomify.com/CVE-2025-66507/): 1Panel – CAPTCHA Bypass via Client-Controlled Flag (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-34410 is a high-severity vulnerability in LXware 1Panel, published on 10 Dec 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: There is no known exploitation of CVE-2025-34410 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/1Panel-dev/1Panel (Go): affected all versions; no fix listed
- github.com/1Panel-dev/1Panel (Go): affected from 1.10.33 up to 2.0.15; no fix listed
- github.com/1Panel-dev/1Panel (Go): affected from 1.10.33 up to 2.0.15; no fix listed

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-34410/ (Markdown: https://insights.sbomify.com/CVE-2025-34410/index.md)
```

## Sources

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

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