# CVE-2018-25381: Joomla Responsive Portfolio 1.6.1 SQL Injection via filter parameters

> Authenticated attackers can execute arbitrary SQL commands via filter parameters to extract sensitive database information from the Joomla Responsive Portfolio plugin.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 May 2026
- **Updated:** 26 May 2026
- **Also known as:** GHSA-hrjv-472v-7gw8

## What is CVE-2018-25381?

CVE-2018-25381 is a high-severity SQL injection vulnerability in Extro Responsive Portfolio, published on 25 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Joomla Responsive Portfolio 1.6.1 contains an SQL injection vulnerability that allows authenticated attackers to execute arbitrary SQL commands through multiple filter parameters. Attackers can inject malicious SQL code via the filter_type_id, filter_pid_id, and filter_search parameters in POST requests to extract sensitive database information including credentials and server details.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2018-25381?


## How do I fix CVE-2018-25381?

No fix has been published for CVE-2018-25381 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-25381 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25381 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25381 and fix it if it is affected.

What it is: CVE-2018-25381 is a high-severity SQL injection vulnerability in Extro Responsive Portfolio, published on 25 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25381 exists.

Affected product: Extro Responsive Portfolio. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-25381/ (Markdown: https://insights.sbomify.com/CVE-2018-25381/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-25381
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-25381
- OSV: https://osv.dev/vulnerability/CVE-2018-25381

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-25381/
Summaries are generated and may contain mistakes; the official description above is the record.