CVE-2025-34410: 1Panel CSRF — HIGH

CISO Take

1Panel versions 1.10.33 through 2.0.15 lack CSRF protections on the Change Username endpoint (/settings/panel), allowing an attacker to craft a page that silently changes a victim's username while they hold an authenticated session. The immediate consequence is account lockout and denial of service rather than data theft, but for teams that run 1Panel to manage AI/ML inference servers, model-serving hosts, or GPU workloads, losing panel access during an incident or maintenance window has real operational cost. The EPSS score of 0.00133 places this in the bottom of observed exploitation likelihood despite the top-97th-percentile ranking noted, and there is no public exploit, no Nuclei template, and no CISA KEV listing, so opportunistic mass exploitation is unlikely today. Patch to a version beyond 2.0.15 once available, and in the interim mitigate by requiring re-authentication for account-modifying actions, enforcing SameSite=Strict cookies, and restricting panel access to a VPN or allowlisted IP range rather than exposing /settings/panel directly to the internet.

Sources: NVD EPSS VulnCheck

What is the risk?

Moderate-low overall risk. The vulnerability is trivial to exploit technically (a single crafted HTML form with auto-submit, no authentication bypass needed beyond social engineering to lure a logged-in admin to a malicious page), but impact is limited to account lockout/DoS rather than data exposure, privilege escalation, or code execution. No public PoC, no scanner template, and no KEV listing reduce near-term exploitation likelihood. However, 1Panel is often used as an infrastructure management layer, so losing admin access to the panel — even temporarily — can disrupt operations on whatever it manages, including AI/ML hosts.

How does the attack unfold?

Reconnaissance

Attacker identifies a publicly exposed 1Panel instance, potentially managing AI/ML infrastructure, and crafts a CSRF payload page.

Delivery

Attacker lures the authenticated panel administrator to the malicious page via phishing or a compromised site.

Exploitation

The victim's browser auto-submits a forged username-change request using their valid session cookies, since no CSRF token or Origin/Referer check exists.

AML.T0049

Impact

The victim is logged out and locked out of the 1Panel admin interface, disrupting management of any AI/ML services hosted behind it.

Reconnaissance

Attacker identifies a publicly exposed 1Panel instance, potentially managing AI/ML infrastructure, and crafts a CSRF payload page.

Delivery

Attacker lures the authenticated panel administrator to the malicious page via phishing or a compromised site.

Exploitation

The victim's browser auto-submits a forged username-change request using their valid session cookies, since no CSRF token or Origin/Referer check exists.

AML.T0049

Impact

The victim is logged out and locked out of the 1Panel admin interface, disrupting management of any AI/ML services hosted behind it.

What systems are affected?

Package	Ecosystem	Vulnerable Range	Patched
1Panel	—	—	No patch

Do you use 1Panel? You're affected.

How severe is it?

CVSS 3.1

N/A

EPSS

0.2%

chance of exploitation in 30 days

Higher than 5% of all CVEs

Source: EPSS v3 — FIRST.org

Exploitation Status

No known exploitation

Sophistication

Trivial

What should I do?

1 step

1) Upgrade 1Panel beyond version 2.0.15 as soon as a patched release is available; monitor the project's GitHub releases page. 2) Until patched, do not expose the 1Panel admin interface (/settings/panel and related endpoints) directly to the public internet — place it behind a VPN, SSH tunnel, or IP allowlist. 3) Configure session cookies with SameSite=Strict and Secure flags at the reverse proxy layer if the application does not set them natively. 4) Add web application firewall (WAF) rules to require a valid Origin/Referer header matching the panel's own domain for state-changing POST requests to /settings/panel. 5) Monitor logs for unexpected username-change events correlated with external referrers, and alert admins if their account is renamed unexpectedly. 6) As a detection measure, review browser extensions or session hygiene practices for staff who keep 1Panel sessions open in the same browser used for general web browsing.

What does CISA's SSVC say?

Decision Track

Exploitation none

Automatable No

Technical Impact partial

Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.

How is it classified?

DoS Auth Bypass Inference

Which compliance frameworks are affected?

This CVE is relevant to:

NIST AI RMF

MANAGE-4.1 - AI system incident response and recovery mechanisms

OWASP LLM Top 10

LLM10 - Unbounded Consumption / Infrastructure Availability

Frequently Asked Questions

What is CVE-2025-34410?

1Panel versions 1.10.33 through 2.0.15 lack CSRF protections on the Change Username endpoint (/settings/panel), allowing an attacker to craft a page that silently changes a victim's username while they hold an authenticated session. The immediate consequence is account lockout and denial of service rather than data theft, but for teams that run 1Panel to manage AI/ML inference servers, model-serving hosts, or GPU workloads, losing panel access during an incident or maintenance window has real operational cost. The EPSS score of 0.00133 places this in the bottom of observed exploitation likelihood despite the top-97th-percentile ranking noted, and there is no public exploit, no Nuclei template, and no CISA KEV listing, so opportunistic mass exploitation is unlikely today. Patch to a version beyond 2.0.15 once available, and in the interim mitigate by requiring re-authentication for account-modifying actions, enforcing SameSite=Strict cookies, and restricting panel access to a VPN or allowlisted IP range rather than exposing /settings/panel directly to the internet.

Is CVE-2025-34410 actively exploited?

No confirmed active exploitation of CVE-2025-34410 has been reported, but organizations should still patch proactively.

How to fix CVE-2025-34410?

1) Upgrade 1Panel beyond version 2.0.15 as soon as a patched release is available; monitor the project's GitHub releases page. 2) Until patched, do not expose the 1Panel admin interface (/settings/panel and related endpoints) directly to the public internet — place it behind a VPN, SSH tunnel, or IP allowlist. 3) Configure session cookies with SameSite=Strict and Secure flags at the reverse proxy layer if the application does not set them natively. 4) Add web application firewall (WAF) rules to require a valid Origin/Referer header matching the panel's own domain for state-changing POST requests to /settings/panel. 5) Monitor logs for unexpected username-change events correlated with external referrers, and alert admins if their account is renamed unexpectedly. 6) As a detection measure, review browser extensions or session hygiene practices for staff who keep 1Panel sessions open in the same browser used for general web browsing.

What systems are affected by CVE-2025-34410?

This vulnerability affects the following AI/ML architecture patterns: model serving, self-hosted infrastructure management.

What is the CVSS score for CVE-2025-34410?

No CVSS score has been assigned yet.

What is the AI security impact?

Affected AI Architectures

model servingself-hosted infrastructure management

Compliance Controls Affected

NIST AI RMF: MANAGE-4.1

OWASP LLM Top 10: LLM10

What are the technical details?

Original Advisory

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.

Exploitation Scenario

An attacker identifies that a target organization exposes a 1Panel instance managing self-hosted AI infrastructure (e.g., discovered via Shodan/Censys fingerprinting or through reconnaissance of the organization's public IP ranges). The attacker crafts a malicious webpage containing a hidden auto-submitting form that POSTs a new username to the victim's /settings/panel endpoint. The attacker delivers this page via a phishing email or a compromised ad network, timed to when the target admin is likely to have an active, authenticated 1Panel session open in another tab. When the admin visits the page, their browser automatically attaches valid session cookies to the forged request, and the username changes without their knowledge. The admin is immediately logged out and, because they no longer know their new username, cannot log back in — effectively locking the legitimate operator out of the panel that controls the underlying AI/ML host, potentially during a window the attacker exploits for other purposes or simply to cause disruption.

Weaknesses (CWE)

CWE-352 Cross-Site Request Forgery (CSRF)

CWE-352 — Cross-Site Request Forgery (CSRF): The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.

[Architecture and Design] Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. For example, use anti-CSRF packages such as the OWASP CSRFGuard. [REF-330] Another example is the ESAPI Session Management control, which includes a component for CSRF. [REF-45]
[Implementation] Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.

Source: MITRE CWE corpus.