CVE-2025-7863
BaseFortify
Publication date: 2025-07-20
Last updated on: 2025-08-25
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| jeesite | jeesite | to 5.12.1 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-601 | The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-7863 is an Open Redirect vulnerability in thinkgem JeeSite versions up to 5.12.0. It occurs in the redirectUrl function of the ServletUtils.java file, where the URL parameter is user-controllable and not properly validated. This allows an attacker to manipulate the redirect destination, causing users to be redirected to arbitrary external malicious websites. The vulnerability can be exploited remotely and requires user interaction. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can be exploited by attackers to redirect users to malicious websites, potentially facilitating phishing attacks. Users may be tricked into believing they are navigating within a trusted site, leading to credential theft, malware installation, or other malicious activities. The integrity of the application is impacted, but confidentiality and availability are not directly affected. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the affected endpoint `/js/lang/cn` for open redirect behavior. You can use curl or similar HTTP clients to send requests with the `url` parameter set to an external URL and observe if the server redirects to that URL. For example, use the command: `curl -I 'http://<your-jeesite-host>/js/lang/cn?url=http://attacker.com/'` and check if the response includes a redirect (HTTP 3xx) to the external URL. If such redirection occurs, the vulnerability is present. [3]
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to apply the available patch identified by commit hash `3d06b8d009d0267f0255acc87ea19d29d07cedc3` which fixes the open redirect issue in the `redirectUrl` function. Until the patch is applied, you should consider implementing input validation or sanitization on the `url` parameter to restrict redirects to trusted domains only. Additionally, monitor and restrict user input that controls redirection to prevent exploitation. [2]