Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with low-privilege account
-
ExploitSend crafted b_id to pbaptism.php
-
ExecutionInject SQL via unsanitized parameter
-
ImpactRead or modify database records
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated session with at least low-privilege access to the Baptism Information Management System web application (CVSS PR:L), after which the attacker sends a malicious value in the b_id parameter to the pbaptism.php endpoint. No special non-default configuration or user interaction is required (UI:N), and the request is remotely deliverable over the network (AV:N). The primary limiting factors are the authentication requirement and the extremely small deployment base of this niche PHP application; there is no indication the vulnerable endpoint is reachable pre-authentication. |
| Impact | This is a low-to-moderate real-world risk despite the publicly available exploit. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) indicates network-reachable, low-complexity exploitation, but PR:L means an attacker must already hold at least low-level authenticated access to the application, which meaningfully constrains opportunistic abuse. Impact is rated Low across confidentiality, integrity, and availability (VC:L/VI:L/VA:L) with no scope change, consistent with a classic SQL injection that exposes or manipulates database contents rather than yielding full system compromise. Exploit maturity is Proof-of-Concept (E:P), and a public exploit reference exists, but there is NO CISA KEV listing and NO EPSS score was provided in the input, so there is no evidence of active or widespread exploitation - the POC should be treated as a capability, not confirmed in-the-wild use. The dominant mitigating factor is product footprint: itsourcecode projects are student/hobby PHP source-code packages, so even a trivially exploitable flaw has little aggregate internet exposure. Net assessment: a genuine vulnerability with a working POC, but low priority relative to high-severity flaws in widely deployed software - prioritize only if this specific application is confirmed in your environment. |
| Exploit ScenarioDerived | An authenticated low-privilege user of the Baptism Information Management System submits a crafted value in the b_id parameter to pbaptism.php, injecting SQL that the application concatenates into a database query. A public proof-of-concept exists (referenced via a GitHub issue), so the attacker can adapt it directly to enumerate or alter baptism records and potentially extract other database contents. Because the CVSS complexity is Low and the vector is network-based, exploitation is straightforward once the attacker has valid application credentials. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
Authenticated SQL injection in itsourcecode Baptism Information Management System 1.0 allows a low-privilege, logged-in user to inject arbitrary SQL through the b_id parameter of the pbaptism.php endpoint, potentially reading, modifying, or corrupting records in the underlying database. Publicly available exploit code exists - the vulnerability was reported via VulDB and a proof-of-concept submission is linked from a public GitHub issue - and the vendor's freely distributed PHP source means the flawed query pattern is easy to locate and reproduce. Because exploitation requires a valid session (CVSS vector PR:L) and the application has an extremely small deployment base, the practical risk is low-to-moderate, consistent with the assigned CVSS 4.0 base score of 5.3.
RemediationAI
No vendor-released patch or fixed version is identified in the available intelligence (the CPE uses a wildcard version and the references contain no vendor advisory with a fix), so the only robust long-term fix is code-level: rewrite the pbaptism.php query to use parameterized/prepared statements (PDO or mysqli bind parameters) for b_id and audit sibling scripts in the same application for identical concatenation patterns. Until that code change is applied, apply compensating controls with their trade-offs in mind: (1) restrict and audit access to pbaptism.php so that only trusted, authenticated staff accounts can reach it - this does not remove the flaw but removes anonymous reachability, and requires the application to already enforce the PR:L prerequisite correctly; (2) run the application's database account with least privilege (SELECT-only where reads suffice, no FILE, no stacked-query or DDL rights), which blunts data exfiltration and file-write attempts but breaks legitimate write functions if applied too aggressively; (3) deploy a WAF or reverse-proxy rule that blocks SQL metacharacters and common injection signatures in the b_id parameter, accepting that encoded or alternative payloads may bypass signature-based filtering; and (4) enable database query logging and alerting on anomalous SQL from the application host. Given the publicly available exploit code, treat any internet-facing instance as at risk and prioritize the code fix over signature-based mitigations. Reference links for tracking: https://vuldb.com/vuln/416750, https://vuldb.com/cve/CVE-2026-108927, and https://itsourcecode.com/ for any vendor update.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The target is a PHP/MySQL web application distributed as source code by itsourcecode.com. The root cause is CWE-89 (Improper Neutralization of Special Elements used in an SQL Command): the script pbaptism.php takes the b_id request argument and incorporates it into a database query without parameterization or adequate escaping, so attacker-controlled SQL syntax reaches the database engine. The CPE record cpe:2.3:a:itsourcecode:baptism_information_management_system:*:*:*:*:*:*:*:* uses a wildcard version, indicating no specific fixed release is identified in the intelligence feed. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P) and the independent CVSS 3.1 assessment agree on a network-reachable, low-complexity issue that requires prior authentication (PR:L) but no user interaction; the limited C/I/A metrics indicate partial exposure of a single component rather than full system compromise, and the E:P metric corresponds to the publicly available exploit. SQL injection of this class typically enables data exfiltration from application tables, authentication-bypass-style query manipulation, and - depending on the database account's privileges and whether stacked queries or file functions are permitted - potentially broader database manipulation.
Know when Baptism Information Management System gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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:P
Network-reachable low-complexity SQLi requiring a low-privilege account (PR:L), with limited database read/write impact mapped to C:L/I:L/A:L and no scope change.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
3DescriptionCVE.org
A weakness has been identified in itsourcecode Baptism Information Management System 1.0. This vulnerability affects unknown code of the file pbaptism.php. This manipulation of the argument b_id causes sql injection. It is possible to initiate the attack remotely. The exploit has been made available to the public and could be used for attacks.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
SQL injection in itsourcecode Baptism Information Management System 1.0 exposes database contents to remote unauthentica
SQL injection in itsourcecode Baptism Information Management System 1.0 exposes the `/delbaptism.php` endpoint to remote
A vulnerability was determined in itsourcecode Baptism Information Management System 1.0. Rated medium severity (CVSS 6.
A vulnerability was found in itsourcecode Baptism Information Management System 1.0. Rated medium severity (CVSS 6.9), t
SQL injection in itsourcecode Baptism Information Management System 1.0 allows an attacker who already holds a low-privi
EUVD-2026-97827
GHSA-32p2-gf6p-43qf
NVD
CVE.org
EPSS
VulDB
Exploit-DB