CVE-2026-23525
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · unedited1Panel 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceStored XSS vulnerability in 1Panel's App Store allows attackers to embed malicious JavaScript in application README content rendered by the MdEditor component with previewOnly enabled, leading to session hijacking via cookie theft and unauthorized system actions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.10.34>= 2.0.0, < 2.0.17CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed 1Panel versionRun `1pctl version` or `docker ps | grep 1panel` to identify the container, then check the image tag. Alternatively, log into the 1Panel web UI and check the version displayed in the footer or About page.Affected if The installed version is below 1.10.34 (for 1.x branch) or below 2.0.17 (for 2.x branch). Versions 2.0.0-2.0.16 are affected.
-
Confirm App Store module is in useLog into the 1Panel web interface and navigate to the App Store section. Verify that application README files are being viewed or edited.Affected if The App Store feature is actively used to browse or view application details containing README markdown content.
-
Identify MdEditor previewOnly configurationInspect the 1Panel source code or configuration files for MdEditor component usage with the `previewOnly` flag set to true. This is typically found in the App Store README rendering logic.Affected if The MdEditor component is configured with `previewOnly: true` in the App Store README rendering context.
-
Audit App Store README content for XSS payloadsReview markdown content in installed apps within the App Store. Check README files for script tags, event handlers (onclick, onerror), javascript: URIs, or other suspicious JavaScript injection patterns.Affected if Any README content in the App Store contains unsanitized HTML/script tags or JavaScript event handlers that could execute when rendered.
A user is affected if they are running 1Panel version below 1.10.34 (or 2.0.0-2.0.16) AND have the App Store accessible with the MdEditor previewOnly mode rendering untrusted markdown content containing malicious JavaScript.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.10.342.0.17
Upgrade to v1.10.34-lts or v2.0.17 which implements proper XSS sanitization in the MdEditor component when rendering markdown content.
v1.10.34-lts (for 1.x users) or v2.0.17 (for 2.x users)
- 1. Backup your current 1Panel installation and data before proceeding with any upgrade
- 2. For v1.x users: Upgrade to version 1.10.34-lts (the v1.10.x LTS release)
- 3. For v2.x users: Upgrade to version 2.0.17
- 4. Verify the upgrade was successful by checking the 1Panel version in the web interface or via CLI
- 5. Test the App Store functionality to confirm the XSS vulnerability is remediated
- 6. Clear browser cache and test viewing application details in the App Store to verify the fix
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23525 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-23525 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data