\n```\n\nWhen a victim views the file in browsing mode (e.g."}},{"@type":"Question","name":"How severe is CVE-2025-50183?","acceptedAnswer":{"@type":"Answer","text":"CVE-2025-50183 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance."}},{"@type":"Question","name":"Which packages are affected by CVE-2025-50183?","acceptedAnswer":{"@type":"Answer","text":"CVE-2025-50183 affects the following packages: @openlist-frontend/openlist-frontend (npm). Ecosystems affected: npm."}},{"@type":"Question","name":"How do I fix CVE-2025-50183?","acceptedAnswer":{"@type":"Answer","text":"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."}},{"@type":"Question","name":"How do I detect CVE-2025-50183 in my npm dependencies?","acceptedAnswer":{"@type":"Answer","text":"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."}},{"@type":"Question","name":"How do I mitigate CVE-2025-50183 if there is no patch (or I can't update yet)?","acceptedAnswer":{"@type":"Answer","text":"Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page."}},{"@type":"Question","name":"Is CVE-2025-50183 actively exploited in the wild?","acceptedAnswer":{"@type":"Answer","text":"No public exploit code has been indexed for CVE-2025-50183 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure."}},{"@type":"Question","name":"What is the EPSS score for CVE-2025-50183?","acceptedAnswer":{"@type":"Answer","text":"CVE-2025-50183 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 25th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority."}},{"@type":"Question","name":"What type of vulnerability is CVE-2025-50183?","acceptedAnswer":{"@type":"Answer","text":"CVE-2025-50183 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure."}},{"@type":"Question","name":"When was CVE-2025-50183 published, and has it been updated?","acceptedAnswer":{"@type":"Answer","text":"CVE-2025-50183 was published on June 19, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting."}}]}
NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

CVE-2025-50183 — @openlist-frontend/openli…

MEDIUMFix: OpenListTeam/OpenList-Frontend@7b5ed20

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

Also known asGHSA-2hw3-h8qx-hqqp
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs25th percentile — riskier than 25% of all scored CVEsHighest risk
0.00%0.27%0.54%0.82%0.2%0.3%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

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.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
@openlist-frontend/openlist-frontendnpm
1Kdownloads / week

Description

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

DateEvent
2025-06-17Vulnerability reported
2025-06-17Comminuty Manager confirmed
2025-06-17Fixed

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

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npm@openlist-frontend/openlist-frontendall versions4.0.0-rc.4npm install @openlist-frontend/openlist-frontend@4.0.0-rc.4

Detection & mitigation playbook

Open-source dependency

  1. Detect

    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.

  2. 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.

  3. Workarounds

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

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: ```javascript <script>alert(document.cookie);</script> ``` When a victim views the file in browsing mode (e.g.
O3 Security · Impact-Aware SCA

Is CVE-2025-50183 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2025-50183: @openlist XSS — Fixed in 4.0.0-rc.4