\n```\n\nWhen a victim views the file in browsing mode (e.g."}},{"@type":"Question","name":"How severe is GHSA-2hw3-h8qx-hqqp?","acceptedAnswer":{"@type":"Answer","text":"GHSA-2hw3-h8qx-hqqp 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 GHSA-2hw3-h8qx-hqqp?","acceptedAnswer":{"@type":"Answer","text":"GHSA-2hw3-h8qx-hqqp affects the following packages: @openlist-frontend/openlist-frontend (npm). Ecosystems affected: npm."}},{"@type":"Question","name":"How do I fix GHSA-2hw3-h8qx-hqqp?","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 GHSA-2hw3-h8qx-hqqp is resolved across your whole dependency graph."}},{"@type":"Question","name":"How do I detect GHSA-2hw3-h8qx-hqqp 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match."}},{"@type":"Question","name":"How do I mitigate GHSA-2hw3-h8qx-hqqp if there is no patch (or I can't update yet)?","acceptedAnswer":{"@type":"Answer","text":"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."}},{"@type":"Question","name":"How does O3 Security protect against GHSA-2hw3-h8qx-hqqp?","acceptedAnswer":{"@type":"Answer","text":"O3 pinpoints whether GHSA-2hw3-h8qx-hqqp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed."}},{"@type":"Question","name":"Is GHSA-2hw3-h8qx-hqqp actively exploited in the wild?","acceptedAnswer":{"@type":"Answer","text":"No public exploit code has been indexed for GHSA-2hw3-h8qx-hqqp 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 GHSA-2hw3-h8qx-hqqp?","acceptedAnswer":{"@type":"Answer","text":"GHSA-2hw3-h8qx-hqqp has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 19th 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 GHSA-2hw3-h8qx-hqqp?","acceptedAnswer":{"@type":"Answer","text":"GHSA-2hw3-h8qx-hqqp 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 GHSA-2hw3-h8qx-hqqp published, and has it been updated?","acceptedAnswer":{"@type":"Answer","text":"GHSA-2hw3-h8qx-hqqp was published on June 18, 2025 and was last updated on June 19, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting."}}]}
Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-2hw3-h8qx-hqqp

MEDIUM

OpenList (frontend) allows XSS Attacks in the built-in Markdown Viewer

Also known asCVE-2025-50183
Published
Jun 18, 2025
Updated
Jun 19, 2025
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk19th percentile+0.08%
0.00%0.26%0.52%0.78%0.0%0.3%Dec 25Apr 26Jun 26

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.

Blast Radius

1 pkg affected
📦@openlist-frontend/openlist-frontend

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

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.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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  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 GHSA-2hw3-h8qx-hqqp is resolved across your whole dependency graph.

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

  4. How O3 protects you

    O3 pinpoints whether GHSA-2hw3-h8qx-hqqp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-2hw3-h8qx-hqqp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 GHSA-2hw3-h8qx-hqqp in your dependencies?

O3 detects GHSA-2hw3-h8qx-hqqp across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works