CVE-2025-10115
BaseFortify
Publication date: 2025-09-09
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 |
|---|---|---|
| siemprecms | siemprecms | 1.3.6 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-10115 is a SQL injection vulnerability in SiempreCMS versions up to 1.3.6, specifically in the file user_search_ajax.php. The vulnerability occurs because user inputs, particularly the parameters 'name' or 'userName', are improperly handled and directly incorporated into SQL queries without proper sanitization or use of prepared statements. This allows an attacker to inject malicious SQL code remotely, potentially manipulating the database queries to access or alter data unauthorizedly. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can allow an attacker to remotely execute SQL injection attacks on the affected SiempreCMS system. This can lead to unauthorized access to sensitive data, data manipulation, or disruption of the system's confidentiality, integrity, and availability. Since the exploit is publicly disclosed and easy to perform without authentication, attackers can exploit this vulnerability to compromise the affected system and its data. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for the presence of the vulnerable SiempreCMS version (up to 1.3.6) and specifically the file user_search_ajax.php. One detection method is to look for HTTP POST requests to user_search_ajax.php with parameters like user-search-username or user-search-name containing suspicious SQL injection payloads (e.g., ' OR 1=1--). A practical approach is to monitor network traffic or logs for such requests. Additionally, Google dorking with the query inurl:user_search_ajax.php can help identify vulnerable targets. A sample command to test the vulnerability using curl is: curl -X POST -b "PHPSESSID=<valid_session_id>" -d "action=search&user-search-username=test' OR 1=1--" https://target.com/path/user_search_ajax.php This command sends a crafted POST request to test for SQL injection via the user-search-username parameter. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include disabling or restricting access to the vulnerable user_search_ajax.php file to prevent exploitation. Since no known mitigations or patches are published, it is recommended to replace SiempreCMS versions up to 1.3.6 with a non-vulnerable version or an alternative product. Additionally, implementing web application firewall (WAF) rules to detect and block SQL injection attempts targeting the user-search-username and user-search-name parameters can help reduce risk. Avoid using the affected version until a fix or update is available. [3]