dbcve.org
Wp TabsWordPress extension · Shapedplugin

CVE-2023-25065

HIGH · 8.8 CVSS v3.1 Published 2023-02-14
Fix available
A fix is available. Upgrade to 2.1.15 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Cross-Site Request Forgery (CSRF) vulnerability in ShapedPlugin WP Tabs – Responsive Tabs Plugin for WordPress plugin <= 2.1.14 versions.

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 · moderate confidence

This is a Cross-Site Request Forgery (CSRF) vulnerability in the ShapedPlugin WP Tabs WordPress plugin versions 2.1.14 and earlier. The vulnerability allows an attacker to trick an authenticated administrator into unknowingly submitting malicious requests to the affected WordPress site, potentially leading to unauthorized configuration changes or data manipulation within the plugin's settings.

MitigationUpdate the ShapedPlugin WP Tabs plugin to a version newer than 2.1.14, which should include proper anti-CSRF token (nonce) validation on all state-changing actions and forms.

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 TabsWordPress extension
Affected:< 2.1.15

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Locate the ShapedPlugin WP Tabs plugin installation
    Check your WordPress site's wp-content/plugins/ directory for a folder named 'wp-tabs' or 'shapedplugin-wp-tabs'. Alternatively, log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins to find ShapedPlugin WP Tabs in the list.
    Affected if The plugin folder or listing is not found, meaning the plugin is not installed.
  2. Determine the installed plugin version
    In the WordPress admin dashboard under Plugins > Installed Plugins, find ShapedPlugin WP Tabs and read the version number displayed beneath the plugin name. If using WP-CLI, run: wp plugin list --name='shapedplugin-wp-tabs' --format=table
    Affected if The displayed version is 2.1.14 or any version number lower than 2.1.15.
  3. Confirm the plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify that ShapedPlugin WP Tabs shows as 'Active' or use WP-CLI: wp plugin is-active shapedplugin-wp-tabs
    Affected if The plugin is active and the version is 2.1.14 or earlier.
  4. Identify state-changing plugin features in use
    Navigate to the plugin settings page (usually under a Tabs menu in the admin sidebar). Review any forms or actions that modify plugin configuration, such as creating/editing tabs, changing global settings, or importing/exporting settings.
    Affected if The plugin has active configuration forms and the installed version is 2.1.14 or earlier, making CSRF exploitation possible.

Your environment is affected if ShapedPlugin WP Tabs is installed, active, and running version 2.1.14 or earlier, as this version lacks anti-CSRF nonce validation on its state-changing forms.

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

Update the ShapedPlugin WP Tabs plugin to a version newer than 2.1.14, which should include proper anti-CSRF token (nonce) validation on all state-changing actions and forms.

Recommended fix High confidence

WP Tabs plugin version 2.1.15

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'WP Tabs – Responsive Tabs' in the plugin list
  4. Check if the current version is below 2.1.15
  5. If an update is available, click 'Update Now' to upgrade to version 2.1.15
  6. Alternatively, download version 2.1.15 from the WordPress plugin repository or your account at shapedplugin.com
  7. If auto-update is enabled, the plugin should auto-update to the fixed version

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

Fix this in Wp Tabs Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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