CVE-2019-25698 | Kados R10 GreenBee Request id_to_delete sql injection (Exploit 46505 / EDB-46505)

VDB-355465 · CVE-2019-25698 · EXPLOIT 46505 KADOS R10 GREENBEE REQUEST ID_TO_DELETE SQL INJECTION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 7.4 $0-$5k 0.54+ Summaryinfo A vulnerability was found in Kados R10 GreenBee. It has been classified as critical. Affected by this vulnerability is an unknown functionality of the component Request Handler. This manipulation of the argument id_to_delete causes sql injection. This vulnerability is registered as CVE-2019-25698. Remote exploitation of the attack is possible. Furthermore, an exploit is available. Detailsinfo A vulnerability classified as critical was found in Kados R10 GreenBee (unknown version). Affected by this vulnerability is an unknown code block of the component Request Handler. The manipulation of the argument id_to_delete with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is: Kados R10 GreenBee contains an SQL injection vulnerability that allows attackers to manipulate database queries by injecting SQL code through the id_to_delete parameter. Attackers can send crafted requests with malicious SQL statements in the id_to_delete field to extract or modify sensitive database information. The weakness was published by Mehmet Emiroglu as 46505. The advisory is shared at exploit-db.com. This vulnerability is known as CVE-2019-25698 since 04/05/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue. It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product. The vulnerability is also documented in the vulnerability database at Exploit-DB (46505). Productinfo Vendor Kados Name R10 GreenBee CPE 2.3info 🔒 CPE 2.2info 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 7.7 VulDB Meta Temp Score: 7.4 VulDB Base Score: 7.3 VulDB Temp Score: 6.6 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 8.2 CNA Vector (VulnCheck): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Sql injection CWE: CWE-89 / CWE-74 / CWE-707 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Access: Public Status: Proof-of-Concept Download: 🔒 Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Exploit-DB: 🔒 Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: no mitigation known Status: 🔍 0-Day Time: 🔒 Timelineinfo 04/05/2026 CVE reserved 04/06/2026 +1 days Advisory disclosed 04/06/2026 +0 days VulDB entry created 04/06/2026 +0 days VulDB entry last update Sourcesinfo Advisory: 46505 Researcher: Mehmet Emiroglu Status: Not defined CVE: CVE-2019-25698 (🔒) GCVE (CVE): GCVE-0-2019-25698 GCVE (VulDB): GCVE-100-355465 scip Labs: https://www.scip.ch/en/?labs.20161013 Entryinfo Created: 04/06/2026 08:06 Changes: 04/06/2026 08:06 (80) Complete: 🔍 Cache ID: 99:A77:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸