CVE-2026-1062
BaseFortify
Publication date: 2026-01-17
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 |
|---|---|---|
| xiweicheng | teamwork_management_system | to 2.28.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-918 | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-1062 is a Server-Side Request Forgery (SSRF) vulnerability in the xiweicheng TMS system up to version 2.28.0. It exists in the function 'summary' within the file HtmlUtil.java, where improper validation of the 'url' argument allows an attacker to manipulate the input. This manipulation causes the server to make unauthorized requests to arbitrary destinations. The vulnerability can be exploited remotely, and public proof-of-concept exploits are available. [1, 3, 5]
How can this vulnerability impact me? :
This SSRF vulnerability can allow an attacker to make the server perform unauthorized requests, potentially accessing internal network resources or services that are not directly exposed. This can lead to unauthorized access to sensitive information, compromise of system integrity, or disruption of availability. Since the attack can be initiated remotely and is easy to execute, it poses a moderate security risk to affected systems. [1, 3, 5]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this SSRF vulnerability involves monitoring for unusual outbound requests initiated by the server, especially those targeting internal or unexpected destinations. Since the vulnerability is in the handling of the 'url' argument in the HtmlUtil.java file, you can look for suspicious HTTP requests or logs that include manipulated URL parameters. Specific commands are not provided in the resources, but general approaches include using network monitoring tools like tcpdump or Wireshark to capture outbound traffic from the server, and searching application logs for requests containing suspicious URL parameters. Additionally, reviewing source code or using static analysis tools to identify usage of the vulnerable function may help detect the issue. [1, 3, 5]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing or updating the affected component to a version that is not vulnerable, if available. Since no known countermeasures or mitigations have been documented, it is recommended to restrict the server's ability to make arbitrary outbound requests by implementing network-level controls such as firewall rules to limit outbound traffic. Monitoring and blocking suspicious requests that exploit the 'url' parameter can also help. Applying strict input validation and sanitization on the 'url' argument in the application code is advised if you have the capability to patch the source. Ultimately, avoiding use of the vulnerable version (up to 2.28.0) of xiweicheng TMS is recommended. [3]