CVE-2025-11320
BaseFortify
Publication date: 2025-10-06
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 |
|---|---|---|
| zhuimengshaonian | wisdom-education | 1.0.4 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-434 | The product allows the upload or transfer of dangerous file types that are automatically processed within its environment. |
| CWE-284 | The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-11320 is a vulnerability in the wisdom-education application (up to version 1.0.4) that allows an attacker to upload arbitrary files without proper restrictions through the uploadFile function in UploadController.java. This unrestricted file upload occurs because the application does not properly validate or filter the uploaded files, enabling attackers to remotely upload potentially dangerous files to the server. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to upload malicious files to your server, which can compromise the confidentiality, integrity, and availability of your system. The uploaded files could be used to execute malicious code, disrupt services, or steal sensitive information. Since the attack can be launched remotely and is easy to exploit, it poses a significant security risk. [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring and analyzing requests to the /api/upload/2 interface for arbitrary or suspicious file upload attempts. Since the vulnerability involves unrestricted file uploads via the uploadFile function, you can look for unusual POST requests to this endpoint containing unexpected file types or payloads. Commands to detect this might include using network traffic inspection tools like tcpdump or Wireshark to capture HTTP POST requests to /api/upload/2, or using curl to test the endpoint with crafted upload requests. For example, a curl command to test the upload endpoint could be: curl -X POST -F "file=@malicious_file.php" http://target/api/upload/2 -v. Additionally, scanning server logs for unexpected file uploads or files with suspicious extensions in the upload directory can help detect exploitation attempts. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include disabling or restricting access to the /api/upload/2 upload interface to prevent arbitrary file uploads. Since no known countermeasures or mitigations are currently available for this vulnerability, it is recommended to replace the affected product with an alternative or upgrade to a version that addresses the issue once available. Additionally, implementing network-level controls such as firewall rules to block unauthorized access to the upload endpoint, and monitoring for suspicious activity can help reduce risk until a permanent fix is applied. [2]