Security readout for executives and security teams
Plain-English summary
Joomla Responsive Portfolio 1.6.1 has a SQL injection flaw. A logged-in attacker could manipulate portfolio filter fields to query the site database, potentially exposing credentials, server details, or other sensitive records. Risk is material for public Joomla sites running this extension.
Executive priority
Prioritize remediation for internet-facing Joomla sites where external users can authenticate. The main business risk is database disclosure, including credentials or operational details. If the extension is internal-only and tightly access-controlled, urgency is lower but still should be tracked.
Technical view
CVE-2018-25381 is CWE-89 in Extro Responsive Portfolio 1.6.1. The reported vulnerable inputs are filter_type_id, filter_pid_id, and filter_search in POST requests. CVSS 4.0 is 7.1 High, with network access, low privileges, no user interaction, high confidentiality impact, and limited integrity impact.
Likely exposure
Exposure is limited to Joomla environments using Extro Responsive Portfolio, also referenced as RPC Responsive Portfolio, version 1.6.1. The bundle provides no evidence that other versions or products are affected. Authentication is required, so risk depends on who can log in to the site.
Exploitation context
The source bundle cites an ExploitDB entry, indicating public exploit information exists. The bundle marks CISA KEV status as false, so there is no supplied evidence of known active exploitation. Do not treat this as internet-unauthenticated compromise without additional evidence.
Researcher notes
Evidence names three filter parameters and an authenticated attack path but does not include vendor patch details in the bundle. Treat ExploitDB as evidence of public exploit availability, not proof of active exploitation. Validation should avoid weaponized testing on production systems.
Mitigation direction
- Inventory Joomla sites for Extro Responsive Portfolio or RPC Responsive Portfolio 1.6.1.
- Check vendor, Joomla Extension Directory, and VulnCheck guidance for a fixed release.
- Upgrade if a vendor-supported fixed version is available.
- Disable or remove the extension where it is not required.
- Restrict and review accounts that can authenticate to affected Joomla sites.
- Monitor web and database logs for unusual portfolio filter activity.
Validation and detection
- Confirm extension name and version in Joomla extension management or asset inventory.
- Review exposed Joomla sites where untrusted users can authenticate.
- Check logs for suspicious requests involving the named filter parameters.
- Verify remediation by confirming the vulnerable version is no longer deployed.
- Document any compensating controls if immediate removal or upgrade is not possible.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2018-25381 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.1 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——VulnCheckCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N2.84.2VulnCheckVulnerability scoring details
Base CVSS 4.0 score
7.1HighVector: 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
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- ExploitDB-45491CVE reference, VulnCheck · exploit
- Official Product HomepageCVE reference, VulnCheck · product
- Product ReferenceCVE reference, VulnCheck · product
- VulnCheck Advisory: Joomla Responsive Portfolio 1.6.1 SQL Injection via filter parametersCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.