Simple Task Scheduling System vulnerabilities
6 known vulnerabilities in Simple Task Scheduling System from Simple Task Scheduling System Project. 6 are rated high or critical. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 9.8 Critical severity
Simple Task Scheduling System: Improper Neutralization of Special Elements used in an SQL Command
Simple Task Scheduling System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at /classes/Master.php?f=delete_payment.
- 9.8 Critical severity
Simple Task Scheduling System: Improper Neutralization of Special Elements used in an SQL Command
Simple Task Scheduling System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at /classes/Master.php?f=delete_student.
- 9.8 Critical severity
Simple Task Scheduling System: Improper Neutralization of Special Elements used in an SQL Command
Simple Task Scheduling System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at /classes/Master.php?f=delete_account.
- 9.8 Critical severity
Simple Task Scheduling System: Improper Neutralization of Special Elements used in an SQL Command
Simple Task Scheduling System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at /classes/Master.php?f=delete_schedule.
- 9.8 Critical severity
Simple Task Scheduling System: Improper Neutralization of Special Elements used in an SQL Command
Simple Task Scheduling System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at /classes/Master.php?f=delete_category.
- 9.8 Critical severity
Simple Task Scheduling System: Improper Neutralization of Special Elements used in an SQL Command
A SQL injection vulnerability exists in Simple Task Scheduling System 1.0 when MySQL is being used as the application database. An attacker can issue SQL commands to the MySQL database through the vulnerable "id" parameter.