CVE-2026-11333
Unrestricted File Upload in Tittuvarghese CollegeManagementSystem
Publication date: 2026-06-05
Last updated on: 2026-06-05
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| tittuvarghese | collegemanagementsystem | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-284 | The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. |
| CWE-434 | The product allows the upload or transfer of dangerous file types that are automatically processed within its environment. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows an attacker to perform unrestricted file uploads leading to remote code execution on the server. This can result in unauthorized access, modification, or disclosure of sensitive student data managed by the CollegeManagementSystem.
Such unauthorized access and potential data breaches could lead to non-compliance with data protection regulations like GDPR and HIPAA, which require strict controls to protect personal and sensitive information from unauthorized access and disclosure.
Because the vulnerability enables remote code execution and potential data compromise, organizations using the affected system may face legal and regulatory risks if they fail to secure the system and protect personal data accordingly.
Can you explain this vulnerability to me?
CVE-2026-11333 is a critical security vulnerability in the CollegeManagementSystem that allows an attacker to perform an unrestricted file upload through the Student Data Upload Endpoint located in the file upload_student_data.php.
The vulnerability occurs because the system only checks the client-supplied Content-Type header to be 'application/csv' without properly validating the uploaded file's content or extension.
An attacker can exploit this by uploading a malicious PHP file disguised as a CSV file. The filename is constructed using user-controlled parameters without any extension whitelist, allowing the attacker to append '.php' to the filename.
The uploaded file is stored in a web-accessible directory where PHP execution is allowed, enabling the attacker to execute arbitrary code remotely by accessing the uploaded PHP file.
How can this vulnerability impact me? :
This vulnerability can lead to Remote Code Execution (RCE) on the affected server.
An attacker can upload and execute malicious PHP code remotely, potentially gaining full control over the server hosting the CollegeManagementSystem.
This could result in unauthorized access to sensitive data, modification or deletion of data, disruption of services, and further compromise of the network.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for suspicious HTTP POST requests to the endpoint dashboard_page/forms/upload_student_data.php that include multipart form data with a Content-Type header set to application/csv. Specifically, look for attempts to upload files with PHP code disguised as CSV files.
One way to detect exploitation attempts is to check for the presence of uploaded files with .php extensions in the web-accessible uploads directory (dashboard_page/forms/uploads/), especially files named using user-controlled parameters such as Program, Department, Course, Batch, and Year of Admission.
Suggested commands to detect this vulnerability include:
- Using web server logs, grep for POST requests to the vulnerable endpoint: `grep 'POST /dashboard_page/forms/upload_student_data.php' /var/log/apache2/access.log`
- Search for uploaded PHP files in the uploads directory: `find /path/to/dashboard_page/forms/uploads/ -name '*.php'`
- Use network monitoring tools to detect HTTP requests with Content-Type: application/csv that contain suspicious payloads.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Restrict file uploads by implementing strict server-side validation of uploaded files, including verifying file extensions and content, not relying solely on client-supplied Content-Type headers.
- Disable execution of PHP files in the uploads directory by configuring the web server to prevent execution of scripts in that folder.
- Monitor and remove any suspicious PHP files already uploaded to the uploads directory.
- If possible, temporarily disable the Student Data Upload Endpoint until a patch or fix is available.
- Apply any available updates or patches once the vendor responds or releases a fix.