CVE-2025-34410: 1Panel CSRF in Change Username Functionality Allows Account Lockout
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.
Security readout for executives and security teams
Plain-English summary
This CVE lets an attacker trick a logged-in 1Panel user into unknowingly changing their account username. The likely business impact is administrative account lockout and service disruption, not direct data theft based on the provided sources.
Executive priority
Treat this as a high-priority administrative availability risk for exposed 1Panel deployments. Prioritize confirmation and vendor-guided remediation, especially where 1Panel manages production infrastructure or shared hosting operations.
Technical view
CVE-2025-34410 is a CSRF issue in 1Panel Change Username functionality under /settings/panel. The source states missing anti-CSRF tokens and Origin/Referer validation allow a cross-site request using the victim’s authenticated browser session.
Likely exposure
The source description cites 1Panel versions 1.10.33 through 2.0.15. The structured affected entry only enumerates 1.10.33, so teams should verify installed versions against vendor and advisory records.
Exploitation context
The CVE is not marked KEV, and the provided sources do not show active exploitation. Exploitation requires user interaction: an authenticated victim must visit attacker-controlled content while their session cookies remain valid.
Researcher notes
Evidence supports CSRF-driven username change and account lockout. The provided bundle does not identify a specific fixed version, public exploit, or in-the-wild activity. Avoid assuming broader compromise beyond the stated username-change impact.
Mitigation direction
Check 1Panel vendor releases and advisory guidance for fixed versions.
Upgrade affected 1Panel deployments when vendor guidance identifies a fixed release.
Restrict administrative panel access to trusted networks or VPNs where possible.
Review administrative session handling and reauthentication requirements for sensitive account changes.
Monitor for unexpected username changes, forced logouts, or administrator lockouts.
Validation and detection
Inventory all 1Panel instances and record exact installed versions.
Compare installed versions with the 1.10.33 through 2.0.15 range cited in the source description.
Review the username-change workflow for anti-CSRF tokens or Origin/Referer validation.
Check audit logs for unexplained username changes or account lockout reports.
Confirm remediation against vendor release notes before closing the finding.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-352 · source CWE mapping
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.