CVE-2019-25221: The Responsive Filterable Portfolio plugin for WordPress is vulnerable to SQL Injection via the 'id' parameter

Q: How do I fix CVE-2019-25221?

responsive filterable portfolio: upgrade to newer than 1.0.8. Exact commands for each OS are on this page.

Q: Is CVE-2019-25221 being exploited?

CVE-2019-25221 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2019-25221 affect?

CVE-2019-25221 affects responsive filterable portfolio. Severity is medium (CVSS 6.5). 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 pr

Q: How urgent is CVE-2019-25221?

Priority 33/100. No elevated risk signals yet.

Routine

MEDIUM 6.5UPGRADE

CVE-2019-25221 is a medium-severity flaw (CVSS 6.5) affecting responsive filterable portfolio. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 t

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.5% (top 59%)
CISA exploited list	No
Weakness	CWE-89
Published	2024-12-13
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: i13websolution

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-12-13 04:15 UTCPublished CVE record published
2026-06-17 02:31 UTCUpdated Record last modified

i13websolution responsive filterable portfolio UPGRADE

Affected: <= 1.0.8

Fixed in: newer than 1.0.8

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy responsive-filterable-portfolio || rpm -q responsive-filterable-portfolio || responsive-filterable-portfolio --version

2. UPGRADE to newer than 1.0.8 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade responsive-filterable-portfolio

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade responsive-filterable-portfolio

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-25221?

responsive filterable portfolio: upgrade to newer than 1.0.8. Exact commands for each OS are on this page.

Is CVE-2019-25221 being exploited?

CVE-2019-25221 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-25221 affect?

CVE-2019-25221 affects responsive filterable portfolio. Severity is medium (CVSS 6.5). 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 pr

How urgent is CVE-2019-25221?

Priority 33/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs