<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Cve-2019-25702 — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/cve-2019-25702/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Sun, 05 Apr 2026 21:16:48 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/cve-2019-25702/feed.xml" rel="self" type="application/rss+xml"/><item><title>Kados R10 GreenBee SQL Injection Vulnerability (CVE-2019-25702)</title><link>https://feed.craftedsignal.io/briefs/2026-04-kados-r10-greenbee-sqli/</link><pubDate>Sun, 05 Apr 2026 21:16:48 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-kados-r10-greenbee-sqli/</guid><description>Kados R10 GreenBee is vulnerable to SQL injection via the id_project parameter, allowing attackers to manipulate database queries to extract sensitive information or modify data.</description><content:encoded><![CDATA[<p>Kados R10 GreenBee is susceptible to SQL injection attacks due to improper input validation of the <code>id_project</code> parameter. This vulnerability, identified as CVE-2019-25702, allows a remote attacker to inject arbitrary SQL code into database queries. By crafting malicious requests, an attacker can potentially extract sensitive data, modify existing records, or even gain unauthorized access to the underlying database. The vulnerability was published on April 5, 2026, and poses a significant risk to organizations using affected versions of Kados R10 GreenBee, potentially leading to data breaches and system compromise. Defenders should prioritize patching or mitigating this vulnerability to prevent exploitation.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker identifies a Kados R10 GreenBee instance.</li>
<li>The attacker crafts a malicious HTTP request targeting an endpoint that uses the <code>id_project</code> parameter in a SQL query.</li>
<li>The attacker injects SQL code into the <code>id_project</code> parameter within the crafted HTTP request. For example, <code>id_project=1' OR '1'='1</code>.</li>
<li>The Kados R10 GreenBee application processes the request and executes the injected SQL code against the database.</li>
<li>The database server executes the malicious SQL query, potentially returning sensitive information.</li>
<li>The attacker retrieves the extracted data from the application&rsquo;s response.</li>
<li>Depending on the injected SQL code, the attacker may modify database records.</li>
<li>The attacker may gain unauthorized access to the database and perform further malicious actions.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this SQL injection vulnerability (CVE-2019-25702) can lead to unauthorized access to sensitive database information, including user credentials, financial data, and other confidential records. This can result in data breaches, financial loss, reputational damage, and legal liabilities for affected organizations. The vulnerability allows attackers to read and modify data, potentially disrupting business operations. The CVSS v3.1 score of 8.2 highlights the severity of this issue.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Apply available patches or upgrades for Kados R10 GreenBee to address CVE-2019-25702.</li>
<li>Deploy the Sigma rule <code>Detect Suspicious SQL Injection Attempts in Kados R10 GreenBee</code> to your SIEM to detect exploitation attempts by monitoring HTTP request parameters.</li>
<li>Implement input validation and sanitization for all user-supplied data, especially for parameters used in database queries, to prevent SQL injection attacks.</li>
<li>Monitor web server logs for suspicious activity, such as unusual characters or SQL keywords in the <code>id_project</code> parameter of HTTP requests, as shown in the log source for the Sigma rules below.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>sql-injection</category><category>web-application</category><category>cve-2019-25702</category></item></channel></rss>