VulnerabilityPublished 19 Jun 2025Updated 23 Jun 2025

CVE-2025-50183: OpenListTeam OpenList · Cross-site Scripting

Affects OpenListTeam OpenListSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 4.0.0-rc.4 when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.0.0-rc.4

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade openlistteam/OpenList-Frontend to 4.0.0-rc.4.

Affected software

Product	Affected	Fixed in
GitHubopenlistteam/OpenList-Frontend`pkg:github/openlistteam/OpenList-Frontend`Other threats	Affected <4.0.0-rc.4	Fixed in 4.0.0-rc.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Immediate upgrade: Organizations should upgrade OpenList to version 4.0.0-rc.4 or later, where the vulnerability is patched.
Input validation and sanitization: Until the upgrade is applied, implement strict input validation and sanitization on the server side to prevent execution of embedded scripts in .py files or any file previews.
Content Security Policy (CSP): Deploy a robust CSP header to restrict the execution of inline scripts and limit the sources from which scripts can be loaded, reducing the impact of any injected scripts.
User awareness: Educate users about the risks of opening or previewing untrusted files within OpenList, emphasizing caution with .py files or files from unknown sources.
Access controls: Restrict file upload and browsing permissions to trusted users only, minimizing the chance of malicious files being introduced.
Monitoring and logging: Enable detailed logging of file preview activities and monitor for unusual patterns or attempts to access suspicious files.
Web Application Firewall (WAF): Configure WAF rules to detect and block common XSS payloads targeting the file preview feature.
Incident response readiness: Prepare to respond to potential exploitation attempts by having processes in place to quickly investigate and remediate incidents involving OpenList.

Description

OpenList Frontend is a UI component for OpenList. Prior to version 4.0.0-rc.4, 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. This issue has been patched in version 4.0.0-rc.4.

Impact

For European organizations using OpenList versions prior to 4.0.0-rc.4, this vulnerability poses a significant risk to confidentiality. An attacker can inject malicious scripts that execute in the browsers of users who preview or browse .py files, potentially leading to session hijacking, data theft, or unauthorized actions performed on behalf of the user. While the vulnerability does not affect integrity or availability directly, the confidentiality breach can have severe consequences, especially for organizations handling sensitive or regulated data such as personal information, intellectual property, or financial records. The risk is heightened in sectors like finance, healthcare, government, and critical infrastructure, where data confidentiality is paramount. Additionally, since no authentication is required to exploit the vulnerability, attackers can target any user with access to the vulnerable OpenList instance, increasing the attack surface. The requirement for user interaction means that social engineering or phishing tactics could be used to lure users into triggering the exploit. The lack of known exploits in the wild suggests the threat is currently theoretical but could become active if attackers develop proof-of-concept code. European organizations should consider the potential for targeted attacks exploiting this vulnerability, especially given the increasing regulatory scrutiny around data protection (e.g., GDPR).

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Jun 2025, 02:46 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats