CVE-2018-25394
SQL Injection in Kados R10 GreenBee
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 |
|---|---|---|
| kados | r10_greenbee | to r10_greenbee (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-25394 is a high-severity SQL injection vulnerability in Kados R10 GreenBee. It occurs because the release_id parameter in the update_release.php file is not properly sanitized before being used in SQL queries. This allows unauthenticated attackers to inject malicious SQL code by sending a crafted GET request.
By exploiting this flaw, attackers can execute arbitrary SQL commands, including UNION-based payloads, to extract sensitive database information such as the current database user, database name, and DBMS version.
How can this vulnerability impact me? :
This vulnerability can have a significant impact because it allows attackers to access sensitive database information without any authentication.
- Attackers can extract confidential data such as usernames, database names, and software versions.
- It compromises the confidentiality of the database.
- Because the vulnerability is remotely exploitable without any privileges or user interaction, it poses a high risk.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by sending crafted HTTP GET requests targeting the release_id parameter in the update_release.php file and observing the server's response for injected SQL data.
A typical detection method involves using curl or similar tools to send a GET request with a UNION SELECT payload to extract database information such as the current user, database name, or DBMS version.
- curl "http://<target>/boards_buttons/update_release.php?release_id=1' UNION SELECT user(), database(), version()-- -"
- Observe the HTTP response for database information concatenated from the injected query, which confirms the vulnerability.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include sanitizing and validating the release_id parameter to prevent SQL injection.
Applying input validation, using prepared statements or parameterized queries, and restricting direct concatenation of user input into SQL queries are essential.
Additionally, restricting access to the vulnerable endpoint and monitoring for suspicious requests can help reduce risk until a patch or update is applied.