CVE-2025-15392
Remote SQL Injection in Kohana KodiCMS Search API Endpoint
Publication date: 2025-12-31
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| kohana | kodicms | 13.82.135 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-15392 is a SQL injection vulnerability in Kohana KodiCMS versions up to 13.82.135. It exists in the Search API Endpoint, specifically in the like() function of the file cms/modules/pages/classes/kodicms/model/page.php. The vulnerability occurs because the user-supplied 'keyword' argument is passed directly into a raw SQL expression without proper sanitization or escaping, allowing attackers to inject malicious SQL code. This can be exploited remotely without authentication, enabling attackers to manipulate database queries. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to exfiltrate sensitive data such as user credentials, API keys, and configuration details. It can enable authentication bypass by cracking extracted admin password hashes, disclose database schema information to facilitate further attacks, and potentially lead to remote code execution in certain MySQL configurations. Overall, it compromises the confidentiality, integrity, and availability of the affected system. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring requests to the `/backend/api-pages.search` GET endpoint for suspicious or malicious `search` parameter values that attempt SQL injection payloads such as `' OR '1'='1` or payloads using `EXTRACTVALUE()`. Detection can also be aided by using Google Dorking to search for the vulnerable file path `cms/modules/pages/classes/kodicms/model/page.php`. Additionally, deploying Web Application Firewall (WAF) rules to detect SQL injection attempts is recommended. Specific commands are not provided, but monitoring HTTP GET requests for suspicious parameters and using WAF logs are practical approaches. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the vulnerable code line `->param(':query', DB::expr($keyword));` with a safe alternative such as `->param(':query', strtolower($keyword));` to avoid using raw SQL expressions with user input. Additionally, remove all `DB::expr()` wrappers around user inputs, implement strict input validation and sanitization, use parameterized queries consistently, apply least privilege principles to database accounts, and deploy Web Application Firewall (WAF) rules to detect and block SQL injection attempts. Since no official patch is available, these workarounds are critical to reduce risk. [1, 2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows attackers to perform SQL injection attacks that can lead to full data exfiltration of sensitive information such as user credentials, API keys, and configuration data. Such unauthorized access and data leakage can result in non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive data against breaches. Therefore, exploitation of this vulnerability could compromise compliance with these standards by exposing protected data and failing to maintain confidentiality and integrity. [1, 2]