Quick answers
- Is CVE-2026-108927 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-108927 being exploited in the wild.
- How severe is CVE-2026-108927?
- Medium severity, with a CVSS score of 6.3, published 12 October 2026.
- Which products and versions are affected?
- Itsourcecode Baptism Information Management System 1.0.
- Is there a fix for CVE-2026-108927?
- No fixed version is recorded yet. Use prepared statements and parameterized queries to separate SQL code from user input; implement strict input validation to ensure the b_id parameter matches expected numeric patterns; restrict database user permissions to minimum necessary privileges. 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-108927 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-108927?
- Check whether you run Itsourcecode Baptism Information 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 parameterized queries to separate SQL code from user input; implement strict input validation to ensure the b_id parameter matches expected numeric patterns; restrict database user permissions to minimum necessary privileges.
Technical details
The vulnerability is a SQL injection flaw in the b_id parameter of /pbaptism.php that fails to sanitize user input before incorporating it into SQL queries. An unauthenticated remote attacker can exploit this via HTTP POST requests to execute arbitrary SQL commands, gaining unauthorized database access and the ability to read, modify, or delete records. The proof-of-concept demonstrates time-based blind SQL injection using SLEEP() functions.
Affected products
- itsourcecode Baptism Information Management System 1.0
Timeline
- 2026-09-24: disclosed
- 2026-10-12: advisory