dbcve.org
Responsive Filterable PortfolioWordPress extension · I13websolution

CVE-2023-2119

MEDIUM · 6.1 CVSS v3.1 Published 2023-04-18
Fix available
A fix is available. Upgrade to after 1.0.19 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Responsive Filterable Portfolio plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the search_term parameter in versions up to, and including, 1.0.19 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Responsive Filterable Portfolio WordPress plugin up to version 1.0.19 is vulnerable to reflected Cross-Site Scripting (XSS) via the search_term parameter. The plugin fails to properly sanitize user input and escape output, allowing unauthenticated attackers to inject malicious JavaScript through crafted URLs that execute when users click the malicious link.

MitigationUpdate the plugin to a version beyond 1.0.19, or implement proper input sanitization (such as sanitize_text_field()) and output escaping (such as esc_html() or esc_attr()) on the search_term parameter before rendering.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Responsive Filterable PortfolioWordPress extension
Affected:<= 1.0.19

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify the plugin is installed
    Check your WordPress plugins directory for the 'responsive-filterable-portfolio' folder, or look for 'I13websolution Responsive Filterable Portfolio' in the WordPress admin plugins list
    Affected if The plugin folder exists in wp-content/plugins/ or the plugin appears in your WordPress admin panel
  2. Identify the installed version
    In WordPress admin, go to Plugins > Installed Plugins and look for the version number listed under the Responsive Filterable Portfolio plugin, or check the main plugin file (e.g., i13-filterable-portfolio.php) for the 'Version' header in the plugin comments
    Affected if The version number displayed is 1.0.19 or lower
  3. Confirm the search_term parameter handling exists
    Examine the plugin PHP files for code that handles a 'search_term' GET or POST parameter, typically found in shortcode handlers or AJAX endpoints
    Affected if The plugin code processes a search_term parameter without proper sanitization functions like sanitize_text_field()
  4. Check for missing output escaping on search_term
    Search the plugin source code for the search_term variable being echoed or printed to HTML output without esc_html() or esc_attr() wrapping
    Affected if The search_term value is output directly to the page without escaping functions, making reflected XSS possible

You are affected if the Responsive Filterable Portfolio plugin is installed with version 1.0.19 or lower and your site processes the search_term parameter without sanitization and escaping.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.0.19
Interim mitigation

Update the plugin to a version beyond 1.0.19, or implement proper input sanitization (such as sanitize_text_field()) and output escaping (such as esc_html() or esc_attr()) on the search_term parameter before rendering.

Recommended fix Moderate confidence

latest available version (check WordPress plugin repository for version higher than 1.0.19)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Responsive Filterable Portfolio' in the plugin list
  4. Check if an update is available for this plugin
  5. If an update is available, click 'Update Now' to install the latest version
  6. Alternatively, you can manually download the updated plugin from the official WordPress plugin repository and upload it via Plugins > Add New > Upload Plugin
  7. After updating, verify the plugin is running on the latest version available

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Responsive Filterable Portfolio Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-2119 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-2119 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data