CVE-2017-20279
Received Received - Intake
SQL Injection in Joomla Payage 2.05

Publication date: 2026-06-19

Last updated on: 2026-06-19

Assigner: VulnCheck

Description
Joomla Payage 2.05 contains an SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries by injecting SQL code through the aid parameter. Attackers can send GET requests to index.php with malicious aid values in the make_payment task to extract sensitive database information using boolean-based blind or time-based blind techniques.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-19
Last Modified
2026-06-19
Generated
2026-06-19
AI Q&A
2026-06-19
EPSS Evaluated
N/A
NVD
CVE-2017-20279
EUVD
EUVD-2017-19006
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
joomla payage 2.05
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
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. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2017-20279 is a SQL injection vulnerability found in Joomla Payage version 2.05. It allows unauthenticated attackers to inject malicious SQL code through the 'aid' parameter in GET requests sent to the 'make_payment' task in index.php.

Attackers exploit this flaw using boolean-based blind or time-based blind SQL injection techniques to manipulate database queries and extract sensitive information from the database.

Impact Analysis

This vulnerability can have a significant impact as it allows attackers to extract sensitive database information without authentication.

  • Unauthorized access to confidential data stored in the database.
  • Potential manipulation of database queries leading to data leakage.
  • Compromise of the integrity and confidentiality of the affected Joomla Payage system.
Detection Guidance

This vulnerability can be detected by sending crafted GET requests to the vulnerable Joomla Payage 2.05 component, specifically targeting the 'aid' parameter in the 'make_payment' task to test for SQL injection.

Detection involves using boolean-based blind or time-based blind SQL injection techniques to observe the application's response or delay, indicating vulnerability.

A sample command to test this could be a curl request like:

  • curl "http://target-site/index.php?option=com_payage&task=make_payment&aid=1' AND SLEEP(5)--"

If the response is delayed by the sleep time, it indicates a time-based blind SQL injection vulnerability.

Mitigation Strategies

Immediate mitigation steps include restricting access to the vulnerable component and parameters, such as limiting access to the 'make_payment' task and the 'aid' parameter.

Applying input validation and sanitization on the 'aid' parameter to prevent SQL injection is critical.

If available, updating or patching the Joomla Payage component to a version that fixes this vulnerability is strongly recommended.

As a temporary measure, consider implementing Web Application Firewall (WAF) rules to block malicious SQL injection payloads targeting the 'aid' parameter.

Compliance Impact

The SQL injection vulnerability in Joomla Payage 2.05 allows attackers to extract sensitive database information without authentication. This exposure of sensitive data can lead to violations of data protection regulations such as GDPR and HIPAA, which mandate the protection of personal and sensitive information from unauthorized access.

Because attackers can manipulate database queries and access confidential information, organizations using the vulnerable component may fail to comply with requirements for data confidentiality and integrity under these standards.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2017-20279. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart