Quick answers
- Is CVE-2026-103543 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-103543 being exploited in the wild.
- How severe is CVE-2026-103543?
- Medium severity, with a CVSS score of 6.3, published 1 October 2026.
- Which products and versions are affected?
- Itsourcecode Leave Management System 1.0.
- Is there a fix for CVE-2026-103543?
- No fixed version is recorded yet. Use prepared statements and parameter binding to separate SQL code from user input, implement strict input validation to ensure LEAVTID conforms to expected numeric formats, and minimize database user permissions to limit the scope of potential compromise. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-103543 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-103543?
- Check whether you run Itsourcecode Leave Management System at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
Use prepared statements and parameter binding to separate SQL code from user input, implement strict input validation to ensure LEAVTID conforms to expected numeric formats, and minimize database user permissions to limit the scope of potential compromise.
Technical details
A SQL injection vulnerability exists in /module/leavetype/controller.php where the LEAVTID parameter is not properly sanitized before use in SQL queries. The vulnerability can be exploited remotely with a POST request containing malicious SQL payloads in the LEAVTID parameter. Attackers can extract sensitive data, modify database records, or potentially gain broader system control depending on database permissions.
Affected products
- itsourcecode Leave Management System 1.0
Timeline
- 2026-09-03: disclosed
- 2026-10-01: advisory