CVE-2025-50183 is a medium-severity (CVSS 6.5) Cross-site Scripting (XSS) vulnerability in @openlist-frontend/openlist-frontend. A fix is available for @openlist-frontend/openlist-frontend — see the affected versions and patch details below.
OpenList (frontend) allows XSS Attacks in the built-in Markdown Viewer
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-50183.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2025-50183 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@openlist-frontend/openlist-frontendnpmDescription
XSS via .py file containing script tag interpreted as HTML
Summary
A vulnerability exists in the file preview/browsing feature of the application, where files with a .py extension that contain JavaScript code wrapped in <script> tags may be interpreted and executed as HTML in certain modes. This leads to a stored XSS vulnerability.
Affected Versions
- <= 4.0.0-rc.3
PoC
Create a .py file with arbitrary JavaScript content wrapped in <script> tags. For example:
<script>alert(document.cookie);</script>
When a victim views the file in browsing mode (e.g., a rendered preview), the JavaScript is executed in the browser context.
Attack vector
An attacker can place such a .py file in the system via remote channels, such as:
- Convincing a webmaster to download or upload the file;
- Tricking users into accessing a file link via public URLs.
Required permissions
- None, if public or visitor access is enabled.
- If the file is uploaded by a user with elevated permissions, potential privilege boundaries may be crossed.
User interaction
Yes. The user must manually click to switch to the browsing or preview mode to trigger the script. And seems only when using ISO-8859-1 encoding.
Scope
- Unchanged
(S:U)- The attack does not cross system or privilege boundaries in general. - ⚠️ Controversial edge case: If sensitive preview files are accessible due to misconfiguration, scope could be considered Changed
(S:C).
Impact
- Confidentiality: User information including cookies, login state, and localStorage may be accessed. Some files that only can be viewed via this user will leak too.
- Integrity & Availability: Not directly impacted.
Recommendations
- Treat all previewed file types (including non-HTML like .py) as plain text unless explicitly sanitized.
- Disable rendering modes that can interpret user-uploaded content as HTML.
Timeline
| Date | Event |
|---|---|
| 2025-06-17 | Vulnerability reported |
| 2025-06-17 | Comminuty Manager confirmed |
| 2025-06-17 | Fixed |
Credits
- Discovered by: @zyk2507
- Reported to: The OpenList Team
- Analyzed and confirmed by: @jyxjjj
- Fixed by: @cxw620
- Fixed in:
4.0.0-rc.4
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @openlist-frontend/openlist-frontend | all versions | 4.0.0-rc.4npm install @openlist-frontend/openlist-frontend@4.0.0-rc.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @openlist-frontend/openlist-frontend, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @openlist-frontend/openlist-frontend to 4.0.0-rc.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-50183 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-50183 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-50183. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-50183 in your dependencies?
O3 Security finds CVE-2025-50183 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.