LiveActive security incident?Get immediate response
CVE Record

CVE-2019-25221: Responsive Filterable Portfolio <=1.0.8 - Authenticated (Admin+) SQL Injection

The Responsive Filterable Portfolio plugin for WordPress is vulnerable to SQL Injection via the 'id' parameter in all versions up to, and including, 1.0.8 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2019-25221 affects the WordPress Responsive Filterable Portfolio plugin through version 1.0.8. A SQL injection flaw may allow database information exposure. The provided sources conflict on authentication requirements, so exposure should be confirmed against installed plugin behavior and vendor guidance.

Executive priority

Treat as a moderate-priority web application data exposure risk. Prioritize internet-facing WordPress sites and environments holding sensitive customer or operational data.

Technical view

The issue is CWE-89 SQL injection in the plugin's id parameter, caused by insufficient escaping and query preparation. CVSS 3.1 is 6.5 with high confidentiality impact and no integrity or availability impact. Sources identify versions up to and including 1.0.8 as affected.

Likely exposure

WordPress sites running Responsive Filterable Portfolio version 1.0.8 or older are the likely exposure. The source bundle does not identify other products or confirmed vulnerable configurations.

Exploitation context

The CVE is not listed as KEV in the supplied data. Public sources in the bundle do not confirm active exploitation. Authentication evidence is inconsistent: the title says Admin+, the description says unauthenticated, and CVSS uses low privileges.

Researcher notes

The strongest technical signal is SQL injection through id due to escaping and prepared-query failures. The authentication requirement is unresolved across provided metadata, so validation should document tested privilege level without assuming unauthenticated reachability.

Mitigation direction

  • Inventory WordPress sites for Responsive Filterable Portfolio installations.
  • Upgrade beyond version 1.0.8 if vendor guidance confirms a fixed release.
  • Disable or remove the plugin where it is not business-critical.
  • Review vendor and Wordfence guidance before accepting residual risk.

Validation and detection

  • Check installed plugin version on each WordPress site.
  • Confirm whether version 1.0.9 or later is available and installed.
  • Review web and database logs for suspicious id parameter activity.
  • Verify no public route exposes affected plugin functionality unexpectedly.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
description · low confidence lookup

Database 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 lookup
cve · low confidence lookup

CVE-2019-25221 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2019-25221Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
nik00726Responsive Filterable Portfolio0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-89 · source CWE mapping

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.