HIGH 8.2

CVE-2017-20274: Joomla LMS King SQL Injection Vulnerability – Unauthenticated Database Access

Joomla LMS King Professional version 3.2.4.0 contains an SQL injection flaw that lets unauthenticated attackers manipulate the underlying database without authentication. An attacker can craft a malicious web request targeting the learning path feature, injecting SQL commands through a specific parameter to read sensitive data from the database. This doesn't require the attacker to be logged in or interact with a user—it's a direct attack on the application's database layer.

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-23

NVD description (verbatim)

Joomla LMS King Professional 3.2.4.0 contains an SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries by injecting SQL code through the cp_id parameter. Attackers can send GET requests to index.php with the option=com_lmsking, view=lmsking, layout=learningpath, and task=learningPath parameters to extract sensitive database information.

2 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

The vulnerability exists in the LMS King component's learning path functionality. When the component processes the cp_id parameter in GET requests to index.php (with option=com_lmsking, view=lmsking, layout=learningpath, and task=learningPath), the application fails to properly sanitize or parameterize the input before constructing SQL queries. This allows an attacker to inject arbitrary SQL syntax, enabling unauthorized data extraction. The attack surface is the public-facing web endpoint with no authentication requirement, making it remotely exploitable over the network.

Business impact

An attacker exploiting this flaw gains read access to the Joomla database, potentially exposing user credentials, personal information, course enrollment data, and other sensitive records stored by the LMS. While the vulnerability does not directly enable database modification or deletion (based on the CVSS vector), the confidentiality breach alone can lead to regulatory violations (GDPR, HIPAA, depending on data), reputational damage, and loss of student/customer trust. Organizations hosting training or educational platforms on affected versions face immediate risk of data exposure.

Affected systems

Joomla LMS King Professional version 3.2.4.0 is confirmed vulnerable. No vendor product list was provided in the source data; organizations should verify their exact component version in the Joomla administrator panel under Extensions > Manage Extensions and cross-reference with the component's official release notes to determine if they are running the affected release or a patched successor.

Exploitability

Exploitability is high. The attack requires no authentication, no user interaction, and network access only—a low bar for an internet-facing Joomla site. Crafting a malicious request is straightforward once the vulnerable parameters are known, and the impact (data extraction) is immediate. No exploit code is required beyond standard HTTP GET requests with SQL syntax. This combination of low attack complexity and direct data access makes the vulnerability attractive to attackers.

Remediation

The primary remediation is to upgrade Joomla LMS King Professional to a patched version released after 3.2.4.0. Consult the official LMS King or Joomla security advisories for the specific patch version number and compatibility notes. As an interim measure, consider restricting web access to the vulnerable com_lmsking component at the web application firewall or reverse proxy level, though this is not a substitute for patching. Verify that the component is necessary; if not, disable or uninstall it entirely.

Patch guidance

Obtain and apply the latest patched version of LMS King Professional from the official vendor. Before deploying to production, test the patch in a staging environment to ensure compatibility with your Joomla version, database, and any customizations. Review the vendor's changelog to confirm the SQL injection fix is included. Once patched, validate that the learning path functionality operates normally and that the vulnerable cp_id parameter is now safely handled. Establish a process to monitor for future security updates from the vendor.

Detection guidance

Monitor HTTP request logs for GET requests to index.php containing suspicious parameter patterns, particularly those with option=com_lmsking and layout=learningpath combined with unusual cp_id values containing SQL keywords (SELECT, UNION, OR, --) or special characters (quotes, semicolons, comment symbols). Web application firewalls can be configured with rules to block requests matching SQL injection signatures. Additionally, enable database query logging and search for unexpected SELECT statements originating from the web application user account. Conduct a database access audit to identify any tables that may have been queried by unauthorized requests.

Why prioritize this

This vulnerability merits immediate attention due to its HIGH CVSS score (8.2), unauthenticated network exploitability, and direct data confidentiality impact. Organizations running Joomla LMS platforms handle sensitive educational and personal data; a breach affects both institutional compliance and user privacy. The ease of exploitation and lack of known workarounds make it a priority for rapid patching cycles.

Risk score, explained

The CVSS 3.1 score of 8.2 (HIGH) reflects: (AV:N) network-based attack requiring no special access, (AC:L) low attack complexity with no special conditions, (PR:N) no privilege requirement, (UI:N) no user interaction needed, (S:U) impact limited to the vulnerable component, (C:H) high confidentiality impact through unauthorized data access, (I:L) low integrity impact (no direct modification capability shown), and (A:N) no availability impact. The high confidentiality score dominates the rating due to unrestricted database read access.

Frequently asked questions

Do I need to be logged in to exploit this vulnerability?

No. The SQL injection is exploitable without any authentication. An attacker can send a crafted GET request directly from the internet to any Joomla site running the vulnerable LMS King component version.

What data can an attacker extract?

An attacker can read any data accessible to the Joomla database user account, typically including user accounts, passwords (if not properly hashed), course content, enrollment records, and other LMS metadata. The extent depends on database permissions and what data is stored.

Is there a workaround if we cannot patch immediately?

There is no complete workaround that eliminates the risk. Temporary mitigations include using a web application firewall to block requests with suspicious cp_id parameters, disabling the LMS King component if not actively used, or restricting access to the component via IP whitelisting—but patching is the only definitive fix.

How can we detect if we have been exploited?

Review web server logs for GET requests to index.php with option=com_lmsking, layout=learningpath, and cp_id parameters containing SQL syntax. Check database query logs for unexpected SELECT statements. Conduct a user access audit to identify any unauthorized data exports or unusual account activity.

This analysis is provided for informational purposes to support vulnerability management and risk assessment. The information herein is based on publicly disclosed vulnerability data and general security best practices. Organizations should independently verify the applicability of this vulnerability to their systems, confirm patch availability and compatibility with their specific Joomla and component versions, and conduct thorough testing before applying patches in production environments. SEC.co makes no warranty regarding the completeness, accuracy, or timeliness of this content. Always consult official vendor advisories and security bulletins for authoritative guidance. Unauthorized access to computer systems is illegal; use this information only for legitimate defensive security purposes. Source: NVD (public-domain), retrieved 2026-07-27. Analysis generated by SEC.co (claude-haiku-4-5).