https://feed.craftedsignal.io/tags/sqlinjection/Trending threats, MITRE ATT&CK coverage, and detection metadata — refreshed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioMon, 06 Apr 2026 16:16:35 +0000https://feed.craftedsignal.io/briefs/2026-04-churchcrm-sql-injection/Mon, 06 Apr 2026 16:16:35 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-04-churchcrm-sql-injection/CVE-2026-34402 is a time-based blind SQL injection vulnerability in ChurchCRM versions prior to 7.1.0. Authenticated users with Edit Records or Manage Groups permissions can exploit the PropertyAssign.php endpoint to exfiltrate or modify database content, including user credentials, PII, and configuration secrets.ChurchCRM is an open-source church management system. Prior to version 7.1.0, the application suffers from a time-based blind SQL injection vulnerability (CVE-2026-34402). Authenticated users with either “Edit Records” or “Manage Groups” permissions can exploit this flaw. Successful exploitation allows attackers to exfiltrate or modify any database content, which could include user credentials, personally identifiable information (PII), and configuration secrets. The vulnerable endpoint is PropertyAssign.php. This vulnerability was addressed and fixed in version 7.1.0 of ChurchCRM. Defenders should prioritize patching vulnerable instances to prevent unauthorized access and data breaches.

Attack Chain

1. An attacker gains valid credentials for ChurchCRM, with “Edit Records” or “Manage Groups” permissions. This could be achieved through credential stuffing, password reuse, or other means.
2. The attacker crafts a malicious HTTP request targeting the PropertyAssign.php endpoint. This request contains a SQL injection payload within a parameter processed by the application.
3. The application processes the malicious SQL query, injecting it into the database query without proper sanitization.
4. Due to the blind nature of the SQL injection, the attacker uses time-based techniques (e.g., SLEEP()) to infer information about the database structure and content.
5. The attacker iterates through various SQL injection payloads, slowly extracting sensitive data such as usernames, password hashes, and other PII.
6. The attacker may modify database records to escalate privileges, create new administrative accounts, or sabotage the application’s functionality.
7. The attacker exfiltrates the stolen data.
8. The final objective is to compromise the confidentiality, integrity, and availability of the ChurchCRM database, potentially leading to significant data breaches and reputational damage.

Impact

Successful exploitation of CVE-2026-34402 can have serious consequences. An attacker can gain unauthorized access to sensitive data stored within the ChurchCRM database. This includes user credentials, PII, and configuration secrets. The attacker can also modify database records, potentially disrupting church operations or causing financial harm. Given the sensitive nature of the data often stored in church management systems, the impact of this vulnerability could be substantial. The vulnerability affects ChurchCRM installations prior to version 7.1.0.

Recommendation

• Upgrade ChurchCRM installations to version 7.1.0 or later to remediate CVE-2026-34402.
• Deploy the Sigma rule detecting requests to PropertyAssign.php with sleep commands to your SIEM and tune for your environment.
• Monitor web server logs for suspicious activity targeting the PropertyAssign.php endpoint.
• Implement web application firewall (WAF) rules to block SQL injection attempts.
• Review user access controls within ChurchCRM to ensure that only authorized personnel have “Edit Records” or “Manage Groups” permissions.

]]>highadvisorysqlinjectioncve-2026-34402churchcrmwebserverhttps://feed.craftedsignal.io/briefs/2026-04-easy-blog-sql-injection/Mon, 06 Apr 2026 11:17:03 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-04-easy-blog-sql-injection/A SQL injection vulnerability exists in code-projects Easy Blog Site 1.0 within the login.php file, exploitable remotely by manipulating the username/password parameters, potentially leading to unauthorized database access.A SQL injection vulnerability has been identified in code-projects Easy Blog Site 1.0, specifically affecting the login.php file. This vulnerability allows a remote attacker to inject malicious SQL code through the username and password parameters. The vulnerability, identified as CVE-2026-5646, stems from improper sanitization of user-supplied input, potentially allowing attackers to bypass authentication or extract sensitive data from the application’s database. The exploit has been publicly disclosed, increasing the risk of widespread exploitation. The scope of the impact depends on the database privileges of the account used by the web application.

Attack Chain

1. Attacker identifies the login page (login.php) of the Easy Blog Site 1.0 application.
2. Attacker crafts a malicious SQL injection payload embedded within the username or password parameter.
3. The attacker sends a crafted HTTP POST request to login.php, including the SQL injection payload.
4. The application’s login.php script fails to properly sanitize the username or password input.
5. The unsanitized input is passed directly into an SQL query executed against the database.
6. The injected SQL code is executed by the database server, modifying the query’s behavior.
7. Depending on the injected SQL, the attacker may bypass authentication or extract data.
8. The attacker gains unauthorized access to the application or exfiltrates sensitive data.

Impact

Successful exploitation of this SQL injection vulnerability (CVE-2026-5646) in Easy Blog Site 1.0 can lead to a range of consequences, including unauthorized access to sensitive user data, modification of application data, or complete compromise of the database server. Given the public disclosure of the exploit, vulnerable installations are at high risk of being targeted by attackers seeking to gain unauthorized access or steal data. The impact is higher if the database user has elevated privileges.

Recommendation

• Inspect web server logs for suspicious POST requests to login.php containing SQL syntax within the username or password parameters to identify potential exploitation attempts (see example rule below).
• Apply input validation and sanitization to the username and password parameters in the login.php file to prevent SQL injection, addressing CVE-2026-5646.
• Implement parameterized queries or prepared statements in the application’s database interactions to prevent SQL injection attacks.
• Monitor database logs for anomalous SQL queries originating from the web application to detect potential breaches.
• Deploy a Web Application Firewall (WAF) rule to block requests containing common SQL injection payloads targeting login.php.

]]>highadvisorysqlinjectioncve-2026-5646webapplication