CVE-2018-25399
SQL Injection in Open ISES Project via nearby.php Parameters
Publication date: 2026-05-29
Last updated on: 2026-05-29
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| open_ises_project | open_ises_project | 3.30A |
| open_ises_project | open_ises_project | to 3.30A (inc) |
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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2018-25399 is a high-severity SQL injection vulnerability found in the Open ISES Project version 3.30A or earlier. It exists in the nearby.php file, where unauthenticated attackers can inject malicious SQL code through the tick_lat and tick_lng parameters.
By sending specially crafted GET requests with malicious SQL payloads, attackers can execute arbitrary SQL queries on the database.
This allows attackers to extract sensitive information such as usernames, database names, and version details from the database.
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access to sensitive database information, including usernames, database names, and version details.
Attackers can manipulate SQL queries to extract or potentially alter data, which may compromise the integrity and confidentiality of your database.
Since the vulnerability allows execution of arbitrary SQL commands without authentication, it poses a significant risk of data breach and database compromise.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for suspicious GET requests to the nearby.php file that include unusual or crafted SQL payloads in the tick_lat and tick_lng parameters.
One approach is to use network traffic inspection tools or web server logs to identify requests containing SQL injection patterns targeting these parameters.
For example, you can use command-line tools like curl or wget to test the endpoint with crafted payloads to see if the system is vulnerable.
- curl "http://target/nearby.php?tick_lat=1' OR '1'='1&tick_lng=1' OR '1'='1"
- grep -i "tick_lat" /var/log/apache2/access.log | grep -E "(\' OR \'1\'=\'1|UNION|SELECT)"
Additionally, using vulnerability scanners that support SQL injection detection against the nearby.php endpoint focusing on tick_lat and tick_lng parameters can help identify the issue.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the vulnerable nearby.php endpoint and applying input validation or sanitization on the tick_lat and tick_lng parameters to prevent SQL injection.
If possible, update the Open ISES Project software to a version where this vulnerability is fixed or apply patches provided by the vendor.
As a temporary measure, consider implementing a Web Application Firewall (WAF) to block malicious SQL injection attempts targeting these parameters.
Monitoring logs for suspicious activity and blocking IP addresses that attempt exploitation can also reduce risk.