dbcve.org
Baptism Information Management SystemApplication · Itsourcecode

CVE-2025-10405

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was determined in itsourcecode Baptism Information Management System 1.0. Affected is an unknown function of the file /listbaptism.php. This manipulation of the argument bapt_id causes sql injection. It is possible to initiate the attack remotely. The exploit has been publicly disclosed and may be utilized.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A SQL injection vulnerability exists in the itsourcecode Baptism Information Management System 1.0, specifically in the /listbaptism.php file through the bapt_id parameter. This allows remote attackers to inject arbitrary SQL commands due to unsanitized user input being used in database queries.

MitigationImplement parameterized queries or prepared statements in listbaptism.php to properly sanitize the bapt_id parameter, and audit similar files for additional SQL injection vulnerabilities.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Baptism Information Management SystemApplication
Affected:= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Baptism Information Management System installation
    Search the web server document root for files containing 'Baptism Information Management System' or look for the listbaptism.php file. Common paths may include /var/www/html/, /www/, or C:\inetpub\wwwroot\ on Windows servers.
    Affected if The system is installed and accessible via web browser on the server.
  2. Locate and inspect the listbaptism.php file
    Open the listbaptism.php file in a text editor and search for occurrences of the bapt_id parameter. Check how the parameter is retrieved (e.g., $_GET['bapt_id'] or $_POST['bapt_id']).
    Affected if The file exists and processes the bapt_id parameter without sanitization.
  3. Verify if SQL queries use unsanitized bapt_id input
    In listbaptism.php, look for SQL query lines (SELECT, INSERT, UPDATE, DELETE) that incorporate the bapt_id variable directly. Check if the code uses prepared statements, parameterized queries, or proper escaping functions.
    Affected if SQL queries concatenate or interpolate the bapt_id parameter directly into the query string without using prepared statements or escaping functions.
  4. Confirm the application is reachable over the network
    Attempt to access the listbaptism.php page via HTTP/HTTPS using a browser or curl command (e.g., curl http://TARGET/listbaptism.php).
    Affected if The vulnerable script is accessible over the network, allowing remote attackers to send requests.
  5. Test the bapt_id parameter for SQL injection behavior
    Send a crafted request with SQL injection payload in bapt_id, such as: listbaptism.php?bapt_id=1' OR '1'='1. Observe if the application returns unexpected database errors, different content, or behaves abnormally.
    Affected if The parameter accepts SQL injection payloads and the application responds with database errors or returns data it should not expose.

You are affected if the Baptism Information Management System 1.0 is installed, the listbaptism.php file processes the bapt_id parameter without prepared statements, and the script is accessible over the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries or prepared statements in listbaptism.php to properly sanitize the bapt_id parameter, and audit similar files for additional SQL injection vulnerabilities.

Fix this in Baptism Information Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10405 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10405 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data