# CVE-2026-23525: 1panel App Store vulnerable to Cross-site Scripting > Attackers can inject malicious scripts via App Store content, leading to session theft and unauthorized system access in 1Panel. - **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 18 Jan 2026 - **Updated:** 20 Jan 2026 - **Also known as:** GHSA-mg24-6h5c-9q42 ## What is CVE-2026-23525? CVE-2026-23525 is a medium-severity cross-site scripting vulnerability in 1Panel-dev 1Panel, published on 18 Jan 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link. ### Official description 1Panel is an open-source, web-based control panel for Linux server management. A stored Cross-Site Scripting (XSS) vulnerability exists in the 1Panel App Store when viewing application details. Malicious scripts can execute in the context of the user’s browser, potentially compromising session data or sensitive system interfaces. All versions of 1Panel up to and including v1.10.33-lts and v2.0.16 are affected. An attacker could publish a malicious application that, when loaded by users (locally or remotely), can execute arbitrary scripts. This may result in theft of user cookies, unauthorized access to system functions, or other actions that compromise the confidentiality, integrity, and availability of the system. The vulnerability is caused by insufficient sanitization of content rendered by the MdEditor component with the `previewOnly` attribute enabled. Specifically, the App Store renders application README content without proper XSS protection, allowing script execution during content rendering; and similar issues exist in system upgrade-related components, which can be fixed by implementing proper XSS sanitization in the MdEditor component. These vulnerabilities can be mitigated by applying proper XSS protection and sanitization when rendering content in the MdEditor component. Safe versions with a patch incorporated are v1.10.34-lts and v2.0.17. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2026-23525? It affects 1 product. Products: Fit2cloud 1panel. ## How do I fix CVE-2026-23525? No fix has been published for CVE-2026-23525 yet. Limit exposure of the affected software until one is available. ## Is CVE-2026-23525 being exploited? There is no known exploitation of CVE-2026-23525 in the wild and no public exploit code. ## Other vulnerabilities in 1Panel-dev 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-2026-23525 and fix it if it is affected. What it is: CVE-2026-23525 is a medium-severity cross-site scripting vulnerability in 1Panel-dev 1Panel, published on 18 Jan 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-23525 in the wild and no public exploit code. Affected product: 1Panel-dev 1Panel. No package-level version data is available, so check the vendor advisory linked from the reference page. 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-2026-23525/ (Markdown: https://insights.sbomify.com/CVE-2026-23525/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-23525 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-23525 - OSV: https://osv.dev/vulnerability/CVE-2026-23525 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-23525/ Summaries are generated and may contain mistakes; the official description above is the record.