CVE-2018-25404
SQL Injection in Open ISES Project
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 add_facnote.php file. This vulnerability allows unauthenticated attackers to execute arbitrary SQL commands by injecting malicious code through the ticket_id parameter.
Attackers can exploit this flaw by sending crafted GET requests with malicious SQL payloads, which enables them to extract sensitive database information such as version details and other data.
How can this vulnerability impact me? :
This vulnerability can have serious impacts including unauthorized access to sensitive database information. Attackers can extract critical data by exploiting the SQL injection flaw without needing any authentication.
Such unauthorized data extraction can lead to data breaches, exposure of confidential information, and potential compromise of the affected system's integrity.
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 add_facnote.php endpoint that include unusual or crafted SQL payloads in the ticket_id parameter.
A practical approach is to analyze web server logs or use network monitoring tools to identify requests containing SQL injection patterns targeting the ticket_id parameter.
- Use tools like grep to search web server logs for suspicious requests: grep "add_facnote.php" /var/log/apache2/access.log | grep "ticket_id="
- Use SQL injection detection tools or web application firewalls (WAF) to detect and block malicious payloads targeting the ticket_id parameter.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the vulnerable add_facnote.php endpoint, applying input validation and sanitization on the ticket_id parameter, and deploying a web application firewall (WAF) to block malicious SQL injection attempts.
Additionally, monitoring and blocking suspicious GET requests with crafted SQL payloads can help reduce exploitation risk until a patch or update is applied.