CVE-2025-34430: 1Panel CSRF Panel Name Modification
1Panel versions 1.10.33 through 2.0.15 contain a cross-site request forgery (CSRF) vulnerability in the panel name management functionality. The affected endpoint does not implement CSRF defenses such as anti-CSRF tokens or Origin/Referer validation. An attacker can craft a malicious webpage that submits a panel-name change request; if a victim visits the page while authenticated, the browser includes valid session cookies and the request succeeds. This allows a remote attacker to change the victim’s panel name to an arbitrary value without consent.
Security readout for executives and security teams
Plain-English summary
CVE-2025-34430 lets an attacker change the displayed name of a victim’s 1Panel instance if an authenticated user visits attacker-controlled content. The issue does not show data theft or service outage impact, but it indicates missing CSRF protection in an administrative function.
Executive priority
Treat this as a moderate administrative integrity issue. Prioritize remediation for internet-accessible or broadly reachable 1Panel deployments, but it is not presented as a data breach or remote code execution vulnerability.
Technical view
LXware 1Panel versions 1.10.33 through 2.0.15 are described as missing CSRF defenses for panel name management. The endpoint reportedly lacks anti-CSRF tokens and Origin/Referer validation, allowing a browser-authenticated request to modify the panel name. CVSS v4.0 is 5.1 with low integrity impact.
Likely exposure
Exposure is likely limited to organizations running affected 1Panel versions with authenticated administrators using browsers that can reach the panel. Internet-facing panels increase practical risk, but exploitation still requires user interaction.
Exploitation context
The bundle does not identify active exploitation, and KEV status is false. Successful abuse requires a logged-in victim to visit malicious content, after which the browser may submit the unintended request with valid cookies.
Researcher notes
The affected-version evidence is partly inconsistent: the description names 1.10.33 through 2.0.15, while the affected metadata lists 1.10.33 with unknown default status. Confirm version applicability against vendor releases before broad conclusions.
Mitigation direction
Check 1Panel release notes and vendor guidance for fixed versions.
Upgrade affected 1Panel deployments when a vendor fix is available.
Restrict administrative panel access to trusted networks where feasible.
Reduce administrator exposure to untrusted links during active sessions.
Validation and detection
Inventory 1Panel deployments and record exact versions.
Confirm whether deployments fall within 1.10.33 through 2.0.15.
Review panel audit data for unexpected name changes.
In authorized testing, verify CSRF token and Origin/Referer enforcement.
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.