dbcve.org
Wp Responsive TabsWordPress extension · I13websolution

CVE-2023-2184

MEDIUM · 6.1 CVSS v3.1 Published 2023-06-09
Fix available
A fix is available. Upgrade to 1.1.16 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 WP Responsive Tabs horizontal vertical and accordion Tabs plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the search_term parameter in versions up to, and including, 1.1.15 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 WP Responsive Tabs plugin for WordPress versions up to 1.1.15 contains a reflected cross-site scripting vulnerability. The search_term parameter is not properly sanitized before being output, allowing attackers to inject arbitrary JavaScript via a crafted URL that tricks users into clicking a malicious link.

MitigationUpdate the WP Responsive Tabs plugin to version 1.1.16 or later, which includes proper input sanitization and output escaping for the search_term parameter.

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
Wp Responsive TabsWordPress extension
Affected:< 1.1.16

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
    Log in to WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'WP Responsive Tabs' or 'I13websolution Wp Responsive Tabs' in the list.
    Affected if The plugin appears in the installed plugins list and is activated
  2. Determine the installed version
    In the Plugins list, click on the plugin name or view details to find the version number displayed under the plugin name.
    Affected if The displayed version is lower than 1.1.16 (for example, 1.1.15, 1.1.14, etc.)
  3. Check if the vulnerable parameter is accessible
    Examine the plugin files for the presence of a search_term parameter handling. Look in the plugin PHP files for code that references $_GET['search_term'] or $_REQUEST['search_term'] without sanitization.
    Affected if Code exists that retrieves search_term from user input without proper sanitization like esc_html() or esc_attr()
  4. Inspect HTTP response for XSS vulnerability
    Using a browser or HTTP tool, request a URL with the plugin's tab handling page and add ?search_term=<script>alert(1)</script>. Check if the script tag is reflected unescaped in the response.
    Affected if The search_term value is reflected in the HTML output without encoding or escaping

A user is affected if the WP Responsive Tabs plugin is installed with a version lower than 1.1.16 and the search_term parameter is handled by the vulnerable code.

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 1.1.16 or later
Fixed in 1.1.16
Interim mitigation

Update the WP Responsive Tabs plugin to version 1.1.16 or later, which includes proper input sanitization and output escaping for the search_term parameter.

Recommended fix High confidence

1.1.16

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'WP Responsive Tabs' (or 'horizontal vertical and accordion Tabs') in the plugin list
  4. Click 'Update Now' to update to version 1.1.16 or latest available version
  5. Verify the plugin was updated successfully by checking the version number

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

Fix this in Wp Responsive Tabs Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-2184 — 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-2184 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