CVE-2017-20263: Joomla! FocalPoint SQL Injection – Analysis & Patch Guidance
A vulnerability in the Joomla! FocalPoint Pro/Free component (version 1.2.3) allows attackers to inject SQL commands into website databases without authentication. By crafting a malicious web request with a specially prepared ID parameter, an attacker can extract sensitive data such as user credentials, customer information, or other confidential records stored in the database. This is a remote attack that requires no special access or user interaction—any unauthenticated person on the internet can exploit it.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 8.2 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
- Weaknesses (CWE)
- CWE-89
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-06-19 / 2026-06-22
NVD description (verbatim)
Joomla! Component FocalPoint Pro/Free 1.2.3 contains an SQL injection vulnerability that allows unauthenticated attackers to execute arbitrary SQL queries by injecting malicious code through the id parameter. Attackers can send GET requests to index.php with option=com_focalpoint, view=location, and a crafted id parameter containing SQL commands to extract sensitive database information.
4 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2017-20263 is an unauthenticated SQL injection vulnerability in the FocalPoint Pro/Free Joomla! component version 1.2.3. The vulnerability exists in the location view handler, where the id parameter is passed unsanitized into SQL queries. Attackers craft GET requests to index.php with parameters option=com_focalpoint and view=location, appending SQL metacharacters and commands to the id parameter to manipulate database queries. The attack vector is network-based with low attack complexity, requiring no authentication or user interaction. While the CVSS vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N) reflects high confidentiality impact, integrity is limited and availability is not directly affected by the vulnerability itself.
Business impact
Organizations running vulnerable versions of FocalPoint Pro/Free face immediate risk of data breach. Attackers can extract entire database contents—including user accounts, email addresses, personal information, and any custom data stored in the component's tables. If the Joomla! database contains shared user credentials or authentication tokens, lateral movement to other systems becomes possible. Regulatory exposure exists if the compromised data includes personally identifiable information (PII) subject to GDPR, CCPA, or similar regimes. The public nature of this vulnerability and its ease of exploitation elevate the likelihood of opportunistic attacks.
Affected systems
Joomla! installations running FocalPoint Pro or FocalPoint Free component version 1.2.3 are affected. Any Joomla! site with this component installed and enabled is vulnerable to remote SQL injection attacks. Organizations should audit their Joomla! instances to identify whether this component is present, regardless of whether it is actively used. Legacy or abandoned Joomla! sites may still host this component unknowingly.
Exploitability
This vulnerability carries high exploitability characteristics: no authentication is required, the attack is network-accessible, attack complexity is low, and no special conditions or user interaction are needed. Proof-of-concept exploitation is straightforward—an attacker constructs a URL with SQL injection payloads in the id parameter and sends it via an ordinary GET request. Automated scanning tools can easily identify vulnerable installations. The vulnerability is not listed on the CISA Known Exploited Vulnerabilities (KEV) catalog, but its age (published June 2026) and ease of exploitation suggest it may attract research and tool development.
Remediation
The primary remediation is to immediately upgrade FocalPoint Pro/Free to a patched version released by the vendor. Verify the exact patch version number against the official Joomla! component repository or vendor advisory. As an interim measure before patching, disable or uninstall the FocalPoint component if it is not actively required. Implement Web Application Firewall (WAF) rules to block SQL injection patterns in the id parameter (e.g., detection of SQL keywords, semicolons, or comment sequences). Apply principle of least privilege to the Joomla! database user—restrict it to only the minimum tables and operations needed for normal operation.
Patch guidance
Check the official Joomla! extensions directory and the vendor's advisory page for the patched version addressing CVE-2017-20263. Download and install the update through Joomla!'s component management interface or manually via SFTP. Test the patch in a staging environment before deploying to production. Verify that the update does not break existing customizations or dependent extensions. After patching, confirm that the location view processes the id parameter safely (ideally via parameterized queries or prepared statements). If patches are unavailable or delayed, prioritize disabling the component.
Detection guidance
Monitor web server access logs and application logs for suspicious patterns in requests to index.php with option=com_focalpoint and view=location parameters. Look for id parameter values containing SQL syntax (e.g., UNION, SELECT, OR 1=1, --, /*). Deploy a WAF or intrusion detection system (IDS) rule to flag SQL injection payloads. Query database audit logs (if enabled) for unexpected SELECT statements or errors originating from the FocalPoint component. Check for recent additions of new database users or privilege escalations. Run database integrity checks to detect unauthorized schema modifications. Conduct a baseline scan of your Joomla! installation to confirm the component version.
Why prioritize this
Despite not being on the CISA KEV list, this vulnerability merits immediate attention due to its CVSS 8.2 HIGH severity rating, unauthenticated remote exploitability, and direct access to sensitive database contents. The low attack complexity and lack of prerequisites make it a prime target for both targeted and opportunistic attacks. Any Joomla! site with FocalPoint Pro/Free 1.2.3 exposed to the internet should be treated as actively at-risk. Organizations should prioritize identification and patching of affected systems within 24–48 hours.
Risk score, explained
The CVSS 3.1 score of 8.2 (HIGH) reflects the combination of network accessibility (AV:N), low attack complexity (AC:L), no authentication requirement (PR:N), no user interaction needed (UI:N), and high confidentiality impact (C:H). The attack does not cross security boundaries (S:U) and has limited integrity impact (I:L) but no availability impact (A:N). This rating appropriately captures the severity of an unauthenticated SQL injection that enables data exfiltration. In the context of Joomla! sites hosting customer or internal data, the practical impact may exceed the base score if the compromise leads to identity theft, regulatory violations, or secondary attacks.
Frequently asked questions
How can I tell if my Joomla! site is running the vulnerable FocalPoint component?
Log in to your Joomla! administrator panel, navigate to Extensions > Manage > Manage, and search for 'FocalPoint'. Check the installed version number. You can also query the Joomla! database directly: SELECT * FROM jos_extensions WHERE name LIKE '%focalpoint%'; to list installed versions. If you do not see FocalPoint listed, your site is not affected by this vulnerability.
Can this vulnerability be exploited without directly accessing my Joomla! admin panel?
Yes. This vulnerability requires no administrator access or authentication. Any attacker on the internet can craft a malicious URL and send it to your site's front end. The vulnerability exists in the public-facing component view and does not require login credentials. This makes it particularly dangerous for internet-facing Joomla! sites.
What if I cannot patch immediately due to operational constraints?
Implement compensating controls: (1) Temporarily disable or uninstall the FocalPoint component via the Joomla! Extensions manager if it is not essential. (2) Deploy a WAF rule blocking SQL keywords in the id parameter. (3) Restrict network access to the affected URL pattern using your web server or firewall (e.g., allow only trusted IP ranges). (4) Enable database query logging and monitor for suspicious activity. These measures reduce risk while you plan and test patching.
Will upgrading Joomla! core itself fix this vulnerability?
No. Upgrading Joomla! core does not address vulnerabilities in third-party extensions like FocalPoint. You must update the FocalPoint component itself. Check the official component repository or vendor advisory for the patched version of FocalPoint Pro/Free, then install that update separately from any core Joomla! updates.
This analysis is provided for informational and defensive purposes. SEC.co does not provide legal, compliance, or warranty advice. Vulnerability details and CVSS scores are derived from authoritative sources and reflect conditions as of the publication date; however, vulnerability landscapes evolve and vendor information may change. Organizations are responsible for verifying patch availability, compatibility, and applicability to their specific environment before deployment. Testing in non-production environments is strongly recommended. This document does not constitute a recommendation to deploy any specific patch or configuration and does not substitute for a thorough risk assessment by qualified security professionals. For official patch and remediation guidance, consult the component vendor's security advisory and your Joomla! distribution provider. Source: NVD (public-domain), retrieved 2026-07-27. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2016-20062HIGHSQL Injection in Simply Poll 1.4.1 WordPress Plugin - Unauthenticated Data Theft
- CVE-2016-20063HIGHSQL Injection in Single Personal Message 1.0.3 – Credential & Data Theft Risk
- CVE-2016-20065HIGHUnauthenticated SQL Injection in Product Catalog 8 WordPress Plugin
- CVE-2016-20068HIGHUnauthenticated SQL Injection in WordPress Booking Calendar Contact Form 1.0.23
- CVE-2016-20069HIGHUnauthenticated SQL Injection in WordPress Booking Calendar Contact Form 1.0.23
- CVE-2016-20071HIGHCritical SQL Injection in WordPress 404 Redirection Manager Plugin v1.0
- CVE-2016-20072HIGHBBS e-Franchise WordPress Plugin SQL Injection – Remote Data Exfiltration Risk
- CVE-2016-20073HIGHSQL Injection in Answer My Question 1.3 WordPress Plugin