CVE-2025-34429: 1Panel CSRF Web Port Configuration Change
1Panel versions 1.10.33 - 2.0.15 contain a cross-site request forgery (CSRF) vulnerability in the web port configuration functionality. The port-change endpoint lacks CSRF defenses such as anti-CSRF tokens or Origin/Referer validation. An attacker can craft a malicious webpage that submits a port-change request; when a victim visits it while authenticated, the browser includes valid session cookies and the request succeeds. This allows an attacker to change the port on which the 1Panel web service listens, causing loss of access on the original port and resulting in service disruption or denial of service, and may unintentionally expose the service on an attacker-chosen port.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Modify the 1Panel web port configuration endpoint to include CSRF protections (anti-CSRF tokens and/or strict Origin/Referer validation), since versions 1.10.33 - 2.0.15 lack these defenses.
1Panel web port configuration CSRF defenses = Enable anti-CSRF token and/or enforce Origin/Referer validation - Compensating control
Restrict access to the 1Panel web interface/port at the network level (e.g., firewall/ACL) to reduce the impact of any port-change that could expose the service on an attacker-chosen port.
Event History
Frequently Asked Questions
What is the severity of CVE-2025-34429?
CVE-2025-34429 is classified as a high-severity vulnerability due to its potential for unauthorized actions through CSRF attacks.
How do I fix CVE-2025-34429?
To fix CVE-2025-34429, you should update to 1Panel version 2.0.16 or later, which includes mitigations for the CSRF vulnerability.
What types of attacks can CVE-2025-34429 enable?
CVE-2025-34429 can enable attackers to perform unauthorized port configuration changes on the affected systems through crafted web pages.
Which versions of 1Panel are affected by CVE-2025-34429?
CVE-2025-34429 affects 1Panel versions from 1.10.33 to 2.0.15.
Are there any recommended best practices to prevent CVE-2025-34429?
Implementing CSRF protection such as anti-CSRF tokens and validating Origin/Referer headers are best practices to mitigate the risk of CVE-2025-34429.