CVE-2025-15094
Reflected XSS in FlyCMS User Login redirectUrl Parameter
Publication date: 2025-12-26
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| sunkaifei | flycms | * |
| sunkaifei | flycms | 1.0.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | 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. |
| CWE-94 | The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-15094 is a reflected Cross-Site Scripting (XSS) vulnerability in the FlyCMS application, specifically in the userLogin function of the UserController.java file. The vulnerability occurs because the redirectUrl parameter is not properly sanitized or encoded before being included in the login page. This allows an attacker to craft a malicious URL containing JavaScript code in the redirectUrl parameter, which is then executed in the victim's browser when they visit the URL. This can lead to arbitrary script execution in the context of the user's session. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can allow attackers to execute arbitrary JavaScript code in the browsers of users who visit a specially crafted URL. Potential impacts include session hijacking, theft of user credentials, defacement of the website, or other malicious actions performed on behalf of the user. Since the attack can be launched remotely without authentication, it poses a significant risk to users interacting with the affected FlyCMS login page. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending a crafted HTTP GET request to the /login endpoint with a malicious redirectUrl parameter containing a script payload, then observing if the payload is reflected unencoded in the response. For example, using curl or Python requests to send a request like: curl 'http://<target>/login?redirectUrl="><script>alert(1)</script>' and checking if the script tag appears in the response body unescaped. A proof-of-concept in Python using the requests library is available that demonstrates this detection method. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include avoiding use of the vulnerable FlyCMS version or disabling the affected /login endpoint if possible. Since no official patch or fix is available, consider implementing input validation and output encoding for the redirectUrl parameter to prevent script injection. Additionally, monitor and restrict access to the vulnerable endpoint and educate users about the risk of clicking suspicious links. Considering alternative products or applying web application firewall (WAF) rules to block malicious payloads targeting the redirectUrl parameter can also help reduce risk. [2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not contain information regarding the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.