CVE-2018-25403
SQL Injection in Open ISES Project via city_graph.php p1 Parameter
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 | 3.30 |
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?
The Open ISES Project version 3.30A contains a high-severity SQL injection vulnerability in the city_graph.php file. This vulnerability allows unauthenticated attackers to execute arbitrary SQL commands by injecting malicious code through the p1 parameter.
Attackers exploit this flaw by sending specially crafted GET requests to city_graph.php, which enables them to retrieve sensitive database information such as schema names and other data.
How can this vulnerability impact me? :
This vulnerability can have serious impacts as it allows attackers to access sensitive database information without any authentication.
By exploiting the SQL injection flaw, attackers can extract critical data from the database, potentially leading to data breaches, unauthorized data disclosure, and further exploitation of the system.
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 city_graph.php file that include unusual or crafted SQL payloads in the p1 parameter.
One way to detect exploitation attempts is to analyze web server logs for requests matching the pattern: city_graph.php?p1= followed by SQL injection payloads.
- Use tools like grep to search access logs for suspicious requests, for example: grep "city_graph.php?p1=" /var/log/apache2/access.log
- Use intrusion detection systems (IDS) or web application firewalls (WAF) to detect and alert on SQL injection patterns targeting the p1 parameter.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the vulnerable city_graph.php file and applying input validation or sanitization on the p1 parameter to prevent SQL injection.
If possible, update or patch the Open ISES Project to a version where this vulnerability is fixed.
Additionally, consider deploying a web application firewall (WAF) to block malicious requests targeting the p1 parameter.
Monitoring and blocking suspicious GET requests to city_graph.php can help reduce the risk of exploitation.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in the Open ISES Project 3.30A allows attackers to extract sensitive database information, which could include personal or protected data. Such unauthorized data access can lead to non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding sensitive information against unauthorized access and breaches.
By enabling attackers to retrieve sensitive information through crafted SQL queries, this vulnerability increases the risk of data exposure, potentially violating confidentiality and integrity requirements mandated by these standards.