/

CVE-2026-13551

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) in Baptism Edit Function

CVE-2026-13551

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Database Compromise and Data Manipulation

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A SQL injection vulnerability in the Baptism Information Management System 1.0 allows an attacker to manipulate the ID parameter in /editBaptism.php to interfere with backend database queries.

When user-supplied identifiers are concatenated into SQL without proper sanitization or parameterization, remote attackers may read, modify, or delete sensitive baptism records and related data.

Affected context

The vulnerability occurs in the web-facing edit functionality of the Baptism Information Management System, specifically in /editBaptism.php when processing the ID argument.

It is typically exposed in deployments where:

  • The application accepts ID values from HTTP requests
  • Request parameters are passed directly into SQL queries
  • There is no consistent use of prepared statements or robust input validation

Under these conditions, crafted ID values can alter the structure of the executed SQL.

Exploit preconditions

  • Attack surface: Public or internal web interface endpoint /editBaptism.php
  • Required access: Ability to send HTTP requests to the application (usually unauthenticated or low-privilege user)
  • Trigger point: Submission of a malicious ID parameter that is embedded into an SQL query
  • Why exploitation is possible: The application constructs SQL statements by concatenating untrusted input into query strings, without parameterization or proper escaping, allowing attackers to inject additional SQL syntax.

Why this happens

This issue stems from building SQL queries using string concatenation with values taken directly from HTTP request parameters.

The ID argument is treated as trusted input and inserted into the query without using prepared statements or a safe query builder.

Conceptually, this maps to CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'), and is related to CWE-74: Improper Neutralization of Special Elements in Output, where control characters and metacharacters are not correctly handled before being used in a command-processing context.

Potential impact

  • Unauthorized reading of baptism records and other sensitive personal data
  • Modification or deletion of existing records, impacting data integrity
  • Creation of fraudulent or tampered entries in the database
  • Extraction of authentication data or configuration information stored in the same database
  • Potential pivoting to other parts of the system if the database account has broad privileges

General mitigation guidance

Effective mitigation typically focuses on eliminating direct string-based query construction and reducing trust in user-provided identifiers.

Common defensive patterns include:

  • Using parameterized queries or prepared statements for all database interactions
  • Employing robust ORM or query builders that separate data from command structure
  • Applying strict server-side validation and type checking on identifier parameters (e.g., ensuring ID is numeric)
  • Enforcing least-privilege on database accounts so that the application can perform only the operations it truly needs
  • Centralizing database access logic to make secure patterns easier to enforce across the codebase

How teams detect issues like this

High-level detection approaches often include:

  • Static analysis rules that flag dynamic SQL built via string concatenation with request parameters
  • Code review checklists focusing on any direct use of $_GET, $_POST, or similar constructs in SQL queries
  • Application-layer security policies requiring parameterized queries and prohibiting ad-hoc SQL construction
  • Runtime monitoring and logging that can surface anomalous query patterns indicative of injection attempts
  • Automated scanning tools configured to test web endpoints with typical SQL injection payloads and report suspicious responses

Sources

SourceLink
github.comgithub.com/Hh-176/CVE/issues/2
itsourcecode.comitsourcecode.com/
vuldb.comvuldb.com/cve/CVE-2026-13551
vuldb.comvuldb.com/submit/843568
vuldb.comvuldb.com/vuln/374559
vuldb.comvuldb.com/vuln/374559/cti

Frequently asked

questions

Yes. An attacker who can reach the /editBaptism.php endpoint over the network and control the ID parameter can attempt to exploit the SQL injection remotely.

Typically, only the ability to send HTTP requests to the affected endpoint is required. Depending on how the page is exposed, this may be possible for unauthenticated users or anyone with basic application access.

The most robust fix is to replace all dynamic string-based SQL with parameterized queries or prepared statements, combined with strict validation of the ID parameter and the use of least-privilege database accounts.

Adopt secure coding standards that mandate parameterized queries, avoid raw string concatenation for commands, enforce input validation for all user-supplied data, and integrate automated security checks (static analysis and web security testing) into the development lifecycle.

Find out what's already
exploitable in your codebase.