What is the severity of CVE-2024-11966?

CVE-2024-11966 is classified as a critical severity vulnerability.

How does CVE-2024-11966 affect the system?

CVE-2024-11966 affects PHPGurukul Complaint Management system 1.0 through an SQL injection vulnerability in the /admin/index.php file.

What can attackers do with CVE-2024-11966?

Attackers can exploit CVE-2024-11966 to manipulate the username argument, potentially gaining unauthorized access or executing arbitrary SQL commands.

Is remote exploitation possible with CVE-2024-11966?

Yes, CVE-2024-11966 can be exploited remotely, allowing attackers to target vulnerable systems without physical access.

How can I fix CVE-2024-11966?

To fix CVE-2024-11966, update to the latest version of the PHPGurukul Complaint Management system that patches this SQL injection vulnerability.

Vulnerability/
CVE-2024-11966

critical

9.8

CWE

89 74

28/11/2024

4/12/2024

CVE-2024-11966: PHPGurukul Complaint Management system index.php sql injection

First published: Thu Nov 28 2024(Updated: )

A vulnerability was found in PHPGurukul Complaint Management system 1.0 and classified as critical. This issue affects some unknown processing of the file /admin/index.php. The manipulation of the argument username leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

Credit: cna@vuldb.com

Affected Software	Affected Version	How to fix
PHPGurukul Complaint Management system	=1.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2024-11966?
CVE-2024-11966 is classified as a critical severity vulnerability.
How does CVE-2024-11966 affect the system?
CVE-2024-11966 affects PHPGurukul Complaint Management system 1.0 through an SQL injection vulnerability in the /admin/index.php file.
What can attackers do with CVE-2024-11966?
Attackers can exploit CVE-2024-11966 to manipulate the username argument, potentially gaining unauthorized access or executing arbitrary SQL commands.
Is remote exploitation possible with CVE-2024-11966?
Yes, CVE-2024-11966 can be exploited remotely, allowing attackers to target vulnerable systems without physical access.
How can I fix CVE-2024-11966?
To fix CVE-2024-11966, update to the latest version of the PHPGurukul Complaint Management system that patches this SQL injection vulnerability.

agent/weakness
agent/title
agent/references
agent/type
agent/description
agent/first-publish-date
agent/author
agent/event
collector/mitre-cve
source/MITRE
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/severity
agent/last-modified-date
agent/softwarecombine
agent/tags
agent/source
vendor/phpgurukul
canonical/phpgurukul complaint management system
version/phpgurukul complaint management system/1.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2024-11966?
CVE-2024-11966 is classified as a critical severity vulnerability.
How does CVE-2024-11966 affect the system?
CVE-2024-11966 affects PHPGurukul Complaint Management system 1.0 through an SQL injection vulnerability in the /admin/index.php file.
What can attackers do with CVE-2024-11966?
Attackers can exploit CVE-2024-11966 to manipulate the username argument, potentially gaining unauthorized access or executing arbitrary SQL commands.
Is remote exploitation possible with CVE-2024-11966?
Yes, CVE-2024-11966 can be exploited remotely, allowing attackers to target vulnerable systems without physical access.
How can I fix CVE-2024-11966?
To fix CVE-2024-11966, update to the latest version of the PHPGurukul Complaint Management system that patches this SQL injection vulnerability.