CVE-2025-46337: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in ADOdb ADOdb
ADOdb is a PHP database class library that provides abstractions for performing queries and managing databases. Prior to version 5.22.9, improper escaping of a query parameter may allow an attacker to execute arbitrary SQL statements when the code using ADOdb connects to a PostgreSQL database and calls pg_insert_id() with user-supplied data. This issue has been patched in version 5.22.9.
AI Analysis
Technical Summary
CVE-2025-46337 is a critical SQL Injection vulnerability (CWE-89) found in the ADOdb PHP database abstraction library, specifically affecting versions prior to 5.22.9. ADOdb is widely used in PHP applications to facilitate database interactions across multiple database management systems, including PostgreSQL. The vulnerability arises from improper neutralization of special elements in SQL commands when user-supplied data is passed to the pg_insert_id() function. This improper escaping allows an attacker to inject arbitrary SQL statements, potentially leading to unauthorized data access, data modification, or partial denial of service. The vulnerability is remotely exploitable without authentication or user interaction, as indicated by the CVSS vector (AV:N/AC:L/PR:N/UI:N). The scope is high because the vulnerability affects the confidentiality and integrity of data, with a lesser impact on availability. The vulnerability has been patched in version 5.22.9 of ADOdb, but no known exploits are currently reported in the wild. Given the critical CVSS score of 10, this vulnerability represents a severe risk to any PHP application using vulnerable versions of ADOdb with PostgreSQL backends.
Potential Impact
For European organizations, this vulnerability poses a significant threat, especially to those relying on PHP-based web applications that use ADOdb for database abstraction with PostgreSQL. Exploitation could lead to unauthorized disclosure of sensitive data, including personal data protected under GDPR, resulting in regulatory penalties and reputational damage. Integrity of data could be compromised, affecting business operations, financial records, or customer information. The vulnerability's ease of exploitation without authentication increases the risk of automated attacks and widespread exploitation. Critical infrastructure sectors such as finance, healthcare, government, and e-commerce in Europe could face targeted attacks leveraging this vulnerability, potentially disrupting services and causing financial losses. The cross-border nature of web applications means that attacks could originate from anywhere, complicating incident response and attribution.
Mitigation Recommendations
European organizations should immediately audit their PHP applications to identify usage of ADOdb versions prior to 5.22.9, particularly those interfacing with PostgreSQL databases. Upgrading to ADOdb version 5.22.9 or later is the primary and most effective mitigation. Where immediate upgrade is not feasible, organizations should implement strict input validation and sanitization on all user-supplied data passed to database functions, especially pg_insert_id(). Employing Web Application Firewalls (WAFs) with rules targeting SQL injection patterns can provide temporary protection. Additionally, monitoring database query logs for anomalous or unexpected SQL commands can help detect exploitation attempts. Organizations should also review and restrict database user privileges to minimize potential damage from successful injection attacks. Regular security assessments and penetration testing focused on SQL injection vulnerabilities are recommended to ensure no residual risks remain.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Poland, Sweden, Belgium, Austria
CVE-2025-46337: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in ADOdb ADOdb
Description
ADOdb is a PHP database class library that provides abstractions for performing queries and managing databases. Prior to version 5.22.9, improper escaping of a query parameter may allow an attacker to execute arbitrary SQL statements when the code using ADOdb connects to a PostgreSQL database and calls pg_insert_id() with user-supplied data. This issue has been patched in version 5.22.9.
AI-Powered Analysis
Technical Analysis
CVE-2025-46337 is a critical SQL Injection vulnerability (CWE-89) found in the ADOdb PHP database abstraction library, specifically affecting versions prior to 5.22.9. ADOdb is widely used in PHP applications to facilitate database interactions across multiple database management systems, including PostgreSQL. The vulnerability arises from improper neutralization of special elements in SQL commands when user-supplied data is passed to the pg_insert_id() function. This improper escaping allows an attacker to inject arbitrary SQL statements, potentially leading to unauthorized data access, data modification, or partial denial of service. The vulnerability is remotely exploitable without authentication or user interaction, as indicated by the CVSS vector (AV:N/AC:L/PR:N/UI:N). The scope is high because the vulnerability affects the confidentiality and integrity of data, with a lesser impact on availability. The vulnerability has been patched in version 5.22.9 of ADOdb, but no known exploits are currently reported in the wild. Given the critical CVSS score of 10, this vulnerability represents a severe risk to any PHP application using vulnerable versions of ADOdb with PostgreSQL backends.
Potential Impact
For European organizations, this vulnerability poses a significant threat, especially to those relying on PHP-based web applications that use ADOdb for database abstraction with PostgreSQL. Exploitation could lead to unauthorized disclosure of sensitive data, including personal data protected under GDPR, resulting in regulatory penalties and reputational damage. Integrity of data could be compromised, affecting business operations, financial records, or customer information. The vulnerability's ease of exploitation without authentication increases the risk of automated attacks and widespread exploitation. Critical infrastructure sectors such as finance, healthcare, government, and e-commerce in Europe could face targeted attacks leveraging this vulnerability, potentially disrupting services and causing financial losses. The cross-border nature of web applications means that attacks could originate from anywhere, complicating incident response and attribution.
Mitigation Recommendations
European organizations should immediately audit their PHP applications to identify usage of ADOdb versions prior to 5.22.9, particularly those interfacing with PostgreSQL databases. Upgrading to ADOdb version 5.22.9 or later is the primary and most effective mitigation. Where immediate upgrade is not feasible, organizations should implement strict input validation and sanitization on all user-supplied data passed to database functions, especially pg_insert_id(). Employing Web Application Firewalls (WAFs) with rules targeting SQL injection patterns can provide temporary protection. Additionally, monitoring database query logs for anomalous or unexpected SQL commands can help detect exploitation attempts. Organizations should also review and restrict database user privileges to minimize potential damage from successful injection attacks. Regular security assessments and penetration testing focused on SQL injection vulnerabilities are recommended to ensure no residual risks remain.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2025-04-22T22:41:54.912Z
- Cisa Enriched
- true
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 682d981fc4522896dcbdcc6c
Added to database: 5/21/2025, 9:08:47 AM
Last enriched: 7/3/2025, 6:54:34 PM
Last updated: 1/7/2026, 5:25:32 AM
Views: 48
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-0650: CWE-306 Missing Authentication for Critical Function in OpenFlagr Flagr
CriticalCVE-2025-15474: CWE-770 Allocation of Resources Without Limits or Throttling in AuntyFey AuntyFey Smart Combination Lock
MediumCVE-2025-14468: CWE-352 Cross-Site Request Forgery (CSRF) in mohammed_kaludi AMP for WP – Accelerated Mobile Pages
MediumCVE-2025-9611: CWE-749 Exposed Dangerous Method or Function in Microsoft Playwright
HighCVE-2026-22162
UnknownActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.