packagist package reportIs phpgurukul/complaint_management_system safe ? phpgurukul/complaint_management_system (packagist) has 12 known vulnerabilities, the worst rated HIGH. No malicious-package signal is recorded.
// reach 0 direct dependencies
none carry a known advisory
0 packages depend on it
dependents not yet indexed for this ecosystem
// ai model usage Tracked for PyPI packages. HuggingFace models declare Python dependencies, so packagist packages are not covered.
cvss CVSS v3.1 base score out of 10
epss chance of exploitation in 30 days, 38th percentile of all CVEs
xyz score CyberXYZ composite out of 10
fig. 01 — CVE-2025-57146, the advisory selected below
// 12 advisories CVE CVE-2025-57146 phpgurukul Complaint Management System in PHP 2.0 is vulnerable to SQL Injection in user/reset-password.php via the mobileno parameter. HIGH CVE CVE-2025-57147 A SQL Injection vulnerability was found in phpgurukul Complaint Management System 2.0. HIGH CVE CVE-2025-57150 phpgurukul Complaint Management System in PHP 2.0 is vulnerable to Cross Site Scripting (XSS) in admin/subcategory.php via the categoryName parameter. HIGH CVE CVE-2025-57151 phpgurukul Complaint Management System 2.0 is vulnerable to Cross Site Scripting (XSS) in admin/userprofile.php via the fullname parameter. HIGH CVE CVE-2024-44657 PHPGurukul Complaint Management System 2.0 is vulnerable to SQL Injection via the fromdate and todate parameters in between-date-userreport.php. MEDI CVE CVE-2024-46335 PHPGurukul Complaint Management System 2.0 is vulnerble to Cross Site Scripting (XSS) via the fromdate and todate parameters in between-date-userreport.php. MEDI CVE CVE-2024-44654 PHPGurukul Complaint Management System 2.0 is vulnerable to SQL Injection via the email and mobileno parameters in reset-password.php. MEDI CVE CVE-2024-44658 PHPGurukul Complaint Management System 2.0 is vulnerable to SQL Injection via the subcategory and category parameters in subcategory.php. MEDI CVE CVE-2024-44655 PHPGurukul Complaint Management System 2.0 is vulnerable to Cross Site Scripting (XSS) via the search parameter in user-search.php. MEDI CVE CVE-2025-57149 phpgurukul Complaint Management System 2.0 is vulnerable to SQL Injection in /complaint-details.php via the cid parameter. MEDI CVE CVE-2025-7834 A vulnerability, which was classified as problematic, was found in PHPGurukul Complaint Management System 2.0. MEDI CVE CVE-2025-7802 A vulnerability was found in PHPGurukul Complaint Management System 2.0 and classified as problematic. LOW phpgurukul Complaint Management System in PHP 2.0 is vulnerable to SQL Injection in user/reset-password.php via the mobileno parameter.
Full advisory text at NVD .
// cvss v3.1 vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Scope Unchanged
Confidentiality High
Integrity High
Availability None // questions Is phpgurukul/complaint_management_system safe to install? CyberXYZ does not call a package safe in absolute terms. It records 12 known vulnerabilities for phpgurukul/complaint_management_system (packagist), the worst rated HIGH, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does phpgurukul/complaint_management_system have known vulnerabilities? Yes. CyberXYZ records 12 known vulnerabilities for phpgurukul/complaint_management_system (packagist), the worst rated HIGH. These include CVE-2025-57146, CVE-2025-57147, CVE-2025-57150, CVE-2025-57151, CVE-2024-44657.
How do I check phpgurukul/complaint_management_system before installing? Search phpgurukul/complaint_management_system in CyberXYZ Check at https://cyberxyz.io/check?q=phpgurukul%2Fcomplaint_management_system . The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 13:45 UTC. The most recent advisory here was published 2025-11-17. Updated continuously from NVD, GHSA, OSV and CNA feeds.
Think a verdict here is wrong? Tell us — we respond within 2 business days. Report an issue with this page