CVE-2026-3767: itsourcecode sanitize or validate this input · SQL Injection
Affects itsourcecode sanitize or validate this inputSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 26 Oct 2026, 09:16 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 8 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| itsourcecodesanitize or validate this input | Affected
| Fixed in– |
GitHubltranquility/cve_submitpkg:github/ltranquility/cve_submitOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediately review and update the affected software to a patched version once available from the vendor. 2. Until patches are released, implement strict input validation on the 'teacher_id' parameter, ensuring it only accepts expected data types and formats (e.g., numeric IDs). 3. Refactor the vulnerable code to use parameterized queries or prepared statements to prevent SQL injection. 4. Conduct a thorough code audit of all input handling in the application to identify and remediate similar vulnerabilities. 5. Employ web application firewalls (WAFs) with SQL injection detection rules to provide an additional layer of defense. 6. Monitor logs for unusual database query patterns or repeated failed attempts to exploit the 'teacher_id' parameter. 7. Educate developers on secure coding practices, emphasizing the importance of input sanitization and validation. 8. Restrict access to the /admin/teacher-attendance.php page to trusted users and networks to reduce exposure. 9. Regularly back up databases and verify restoration procedures to mitigate impact in case of successful exploitation.
Description
A weakness has been identified in itsourcecode sanitize or validate this input 1.0. Affected is an unknown function of the file /admin/teacher-attendance.php. Executing a manipulation of the argument teacher_id can lead to sql injection. The attack may be launched remotely. The exploit has been made available to the public and could be used for attacks.