Simple Task Scheduling System Project vulnerabilities
We track 6 vulnerabilities in Simple Task Scheduling System Project products. 6 are rated high or critical, and none are known to be exploited. The most recent was published on August 26, 2022.
Latest Simple Task Scheduling System Project vulnerabilities
- 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.