CVE-2018-25395
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 | * |
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
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in Kados R10 GreenBee allows unauthenticated attackers to extract sensitive database information, including current user data and database details. Such unauthorized access to sensitive information can lead to violations of data protection regulations like GDPR and HIPAA, which mandate the protection of personal and sensitive data against unauthorized access and breaches.
By enabling attackers to retrieve sensitive information through SQL injection, this vulnerability increases the risk of data breaches, potentially resulting in non-compliance with standards that require strict data confidentiality, integrity, and security controls.
Can you explain this vulnerability to me?
Kados R10 GreenBee contains a high-severity SQL injection vulnerability in the update_feature.php file. This vulnerability arises because the feature_id parameter is directly concatenated into SQL statements without proper sanitization.
Unauthenticated attackers can exploit this flaw by sending a crafted GET request with a UNION-based payload through the feature_id parameter. This allows them to execute arbitrary SQL commands on the database.
As a result, attackers can extract sensitive database information such as the current user, database name, and DBMS version.
How can this vulnerability impact me? :
This vulnerability can have significant impacts because it allows unauthenticated attackers to execute arbitrary SQL commands on the database.
- Attackers can extract sensitive information from the database, including user credentials and database details.
- The integrity of the database can be compromised, potentially leading to data leakage.
- Since the vulnerability requires no authentication, it increases the risk of unauthorized access and data exposure.
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 targeting the update_feature.php file, specifically those including the feature_id parameter with unusual or crafted SQL payloads.
A practical detection method is to use network traffic inspection or web server logs to identify requests with UNION-based SQL injection patterns in the feature_id parameter.
For example, you can use the following command to search web server logs for suspicious requests:
- grep -i 'update_feature.php' /var/log/apache2/access.log | grep 'feature_id=.*UNION'
Additionally, tools like sqlmap can be used to test the vulnerability by targeting the feature_id parameter with automated SQL injection payloads.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying input validation and sanitization on the feature_id parameter to prevent SQL injection.
If a patch or update is available from the vendor, it should be applied promptly to fix the vulnerability.
As a temporary measure, you can block or filter HTTP requests containing suspicious SQL injection patterns targeting update_feature.php at the web application firewall or network perimeter.
Review and restrict database permissions to limit the impact of any successful injection.