CVE-2017-20258

Joomla! Component RPC Responsive Portfolio 1.6.1 SQL Injection

No known exploitation. EPSS puts it in the 41st percentile. No fix published yet.

CVSS 3.18.2High EPSS percentile41st0.5% chance in 30 days CISA KEVNot listedNo confirmed exploitation
No public exploit known FixNone yetNo fix or workaround published

Published 2026-06-19Updated 2026-08-19Sources: CVE.org, NVD

NVD CVE.org

What to do

No fixed build or workaround is published yet. Limit exposure and watch for a patch.

Extro RPCAffected: 1.6.1Upgrade to: not statedStated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record

Check whether your Joomla! site has RPC Responsive Portfolio installed and whether its version is 1.6.1.
If it is installed, ask your developer or hosting provider whether the component is publicly reachable and whether it can be removed or disabled.
No fixed version is currently available; do not rely on an upgrade until the vendor publishes one.
Restrict public access to the affected component or disable it while you arrange a replacement or vendor guidance.

May need vendor or contractor work

Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

Joomla! Component RPC Responsive Portfolio 1.6.1 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_pofos&view=pofo&id=[SQL] to extract sensitive database information.

In plain language

Written by AI from the record

Joomla! sites using RPC Responsive Portfolio 1.6.1 should act: an outsider may be able to read sensitive database information.

Unauthenticated network-accessible SQL injection in Joomla! Component RPC Responsive Portfolio 1.6.1 allows malicious database commands through an ID field.

If you're affected

Database data exposure
Customer record exposure
Business information disclosure

What is it

This is a flaw in a website add-on that can let an outsider ask the site's database questions it was never meant to answer. It is like someone slipping altered questions to a filing clerk and receiving pages from locked business records in return.

Who is affected

This matters to you if your Joomla! website uses RPC Responsive Portfolio version 1.6.1. It is especially relevant for sites that store customer, order, account, or other private information in their website database. An attacker does not need an account or a staff member to click anything; it is a risk when the affected component can be reached over the network.

How urgent is it

An attacker can send specially made web requests to a vulnerable site and attempt to extract database information, so treat this as an amber-priority issue. There is no record of confirmed active exploitation or public exploit code, but there is also no published fix, so reduce exposure promptly.

What to do — in detail

Confirm whether the Joomla! installation includes RPC Responsive Portfolio and whether the installed version is 1.6.1. Review whether requests can reach the component from outside your network, including the com_pofos route described in the advisory.

No patched release or fixed version is available in the findings. Do not plan an in-place upgrade as the remedy; contact the component vendor or replace/remove the component after testing the impact on portfolio pages and related site functions.

If patching or replacement is delayed, disable the component or restrict public access to its affected route at the web server, reverse proxy, or application firewall. Review web-server and application logs for unusual requests to index.php using option=com_pofos, view=pofo, or suspicious content in the id parameter, and investigate unexpected database exports or account-data access.

CISA has not added this CVE to its Known Exploited Vulnerabilities catalog, so there is no CISA remediation due date.

Technical context

CVE-2017-20258 is rated CVSS 8.2 High (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N) and maps to CWE-89, SQL injection. The affected Joomla! Component RPC Responsive Portfolio 1.6.1 accepts attacker-controlled SQL through an ID parameter in a network request, enabling confidential database-data extraction without authentication or user interaction. It is not listed in CISA KEV, no public exploit code is on record, and EPSS predicts a 0.5% likelihood (41st percentile) with a flat trend. Patch availability is unknown; no fix information is available.

This is a general assessment based on public vulnerability data. It does not account for your specific infrastructure — when in doubt, consult a security specialist.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS41st

CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.5% chance of exploitation activity in the next 30 days, which ranks it in the 41st percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

5 events over 61 days, from the signal feeds we watch.

2026-08-19Record updated
2026-06-22Record updated
2026-06-19Publishedweakness classified, att&ck mapped

Affected products

Extroaka extro forms, responsive portfolio
- responsive portfolioOn-premWeb & CMS Plugins / site-builder
- RPCOn-premWeb & CMS Plugins / site-builder

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Scored 8.2 by NVD.

How it is reached

Attack Vector NetworkExploitable remotely over the network without any special conditions
Attack Complexity LowNo special conditions — the attack can be reliably reproduced
Privileges Required NoneNo authentication required — anyone can exploit this
User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

Confidentiality HighTotal information disclosure — all data in the component is compromised
Integrity LowData modification is possible but limited in scope or consequence
Availability NoneNo availability impact