CVE-2017-20280
Received Received - Intake
SQL Injection in Joomla Myportfolio Component

Publication date: 2026-06-19

Last updated on: 2026-06-19

Assigner: VulnCheck

Description
Joomla Component Myportfolio 3.0.2 contains an SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries by injecting SQL code through the pid parameter. Attackers can send GET requests to index.php with malicious pid values in the task=project&view=grid endpoint to extract sensitive database information.
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
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
joomla myportfolio 3.0.2
joomla component_myportfolio to 3.0.2 (exc)
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
Compliance Impact

The SQL injection vulnerability in Joomla Component Myportfolio 3.0.2 allows unauthenticated attackers to extract sensitive database information by manipulating SQL queries. This exposure of sensitive data can lead to non-compliance with data protection regulations such as GDPR and HIPAA, which require the protection of personal and sensitive information from unauthorized access.

Specifically, the ability for attackers to extract sensitive information through this vulnerability increases the risk of data breaches, which are subject to strict reporting and remediation requirements under these standards.

Executive Summary

The Joomla Component Myportfolio version 3.0.2 contains a high-severity SQL injection vulnerability identified as CVE-2017-20280. This flaw allows unauthenticated attackers to inject malicious SQL code through the 'pid' parameter in a GET request to the index.php endpoint with task=project&view=grid. By manipulating this parameter, attackers can alter database queries executed by the application.

This vulnerability enables attackers to potentially extract sensitive information from the database by sending specially crafted requests without needing any authentication.

Impact Analysis

This SQL injection vulnerability can have serious impacts including unauthorized access to sensitive database information. Attackers can exploit the flaw to extract confidential data, which may include user information, credentials, or other critical data stored in the database.

Because the vulnerability can be exploited without authentication, it poses a significant risk to the security and integrity of the affected Joomla website and its data.

Detection Guidance

This SQL injection vulnerability can be detected by sending crafted GET requests to the vulnerable Joomla Myportfolio component endpoint and observing the responses for SQL errors or unexpected data.

A typical detection command involves using curl or similar HTTP clients to send requests with malicious payloads in the pid parameter to the URL pattern: index.php?task=project&view=grid&id=1&pid=[SQL]&format=raw&option=com_myportfolio&Itemid=125.

  • Example curl command to test for SQL injection: curl "http://target.com/index.php?task=project&view=grid&id=1&pid=1' OR '1'='1&format=raw&option=com_myportfolio&Itemid=125"
  • Look for SQL error messages or abnormal responses indicating database query manipulation.
Mitigation Strategies

Immediate mitigation steps include updating the Joomla Myportfolio component to a version that patches this SQL injection vulnerability.

If an update is not immediately available, restrict access to the vulnerable endpoint by implementing web application firewall (WAF) rules to block malicious payloads targeting the pid parameter.

Additionally, monitor web server logs for suspicious requests containing SQL injection patterns and consider disabling or restricting the affected component until a fix is applied.

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