<?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>Focalpointx - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/vendors/focalpointx/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Fri, 19 Jun 2026 16:34:10 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/vendors/focalpointx/feed.xml" rel="self" type="application/rss+xml"/><item><title>Joomla! FocalPoint Pro/Free SQL Injection (CVE-2017-20263)</title><link>https://feed.craftedsignal.io/briefs/2026-06-joomla-focalpoint-sqli/</link><pubDate>Fri, 19 Jun 2026 16:34:10 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-06-joomla-focalpoint-sqli/</guid><description>An unauthenticated SQL injection vulnerability (CVE-2017-20263) in Joomla! Component FocalPoint Pro/Free version 1.2.3 allows attackers to execute arbitrary SQL queries via a crafted 'id' parameter in GET requests, leading to sensitive database information disclosure.</description><content:encoded><![CDATA[<p>CVE-2017-20263 details a critical SQL injection vulnerability affecting Joomla! Component FocalPoint Pro/Free version 1.2.3. This vulnerability allows unauthenticated attackers to execute arbitrary SQL queries by manipulating the <code>id</code> parameter within specific GET requests. By crafting malicious SQL code into the <code>id</code> parameter when requesting <code>index.php</code> with <code>option=com_focalpoint</code> and <code>view=location</code>, attackers can force the application to disclose sensitive database information. The vulnerability, first documented in 2026, presents a significant risk to organizations using the affected Joomla! component, potentially leading to unauthorized data exposure and further compromise if database credentials are leaked.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An unauthenticated attacker identifies a vulnerable Joomla! instance running FocalPoint Pro/Free version 1.2.3.</li>
<li>The attacker crafts a malicious HTTP GET request targeting <code>index.php</code> on the vulnerable server.</li>
<li>The request includes specific parameters: <code>option=com_focalpoint</code> and <code>view=location</code>.</li>
<li>The attacker injects SQL commands (e.g., <code>id=1 UNION SELECT USER(), DATABASE()</code>) into the <code>id</code> parameter of this GET request.</li>
<li>The vulnerable FocalPoint component processes the request without proper sanitization, leading to the execution of the attacker-supplied SQL queries against the backend database.</li>
<li>The database responds to these queries, returning sensitive information such as user credentials, database schemas, or application data within the web application's output.</li>
<li>The attacker parses the HTTP response to extract the disclosed sensitive database information.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2017-20263 grants unauthenticated attackers the ability to extract sensitive information directly from the underlying database of the Joomla! application. This can include confidential user data, hashed passwords, session tokens, and configuration details. Such data exfiltration can lead to severe consequences, including further account compromise, unauthorized access to internal systems, or compliance violations. Organizations in any sector using the vulnerable component are at risk of data breaches and reputational damage if their databases are exposed.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Patch CVE-2017-20263 by upgrading the Joomla! FocalPoint Pro/Free component to a version beyond 1.2.3 immediately.</li>
<li>Deploy the Sigma rule &quot;Detects CVE-2017-20263 Exploitation Attempt&quot; to your SIEM system to identify exploitation attempts.</li>
<li>Enable comprehensive web server access logging to capture full HTTP request details, including query strings, which are essential for the detection rule.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>sqli</category><category>web-vulnerability</category><category>joomla</category><category>data-exfiltration</category></item></channel></rss>