Wp TabsWordPress extension · Shapedplugin
CVE-2023-52124
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in ShapedPlugin LLC WP Tabs – Responsive Tabs Plugin for WordPress allows Stored XSS.This issue affects WP Tabs – Responsive Tabs Plugin for WordPress: from n/a through 2.2.0.
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 confidenceA Stored Cross-Site Scripting (XSS) vulnerability exists in the WP Tabs – Responsive Tabs Plugin for WordPress (versions through 2.2.0). The plugin fails to properly sanitize user-supplied input before rendering it in web pages, allowing an attacker to inject malicious JavaScript code that executes in the browsers of users who view the affected content.
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
<= 2.2.0CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify WP Tabs plugin is installedLog into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'WP Tabs - Responsive Tabs' or 'Shapedplugin WP Tabs' in the list of active plugins.Affected if Plugin is present and active in the WordPress installation
-
Determine installed plugin versionIn the Plugins list, locate the WP Tabs entry and note the version number displayed beneath the plugin name. Alternatively, access the main plugin file via FTP or file manager at /wp-content/plugins/wp-tabs/ and inspect the main PHP file (often wp-tabs.php or similar) for a 'Version' constant or header comment.Affected if Version number is 2.2.0 or lower
-
Compare version to affected rangeCompare the installed version found in step 2 against the affected range: any version 2.2.0 or lower is within the vulnerable range.Affected if Installed version is 2.2.0 or lower
-
Identify tabs with user-supplied contentNavigate to WP Tabs settings in the admin dashboard (usually under a menu item created by the plugin). Review each tab configuration to identify which tabs accept or display user-submitted content, as these are the potential injection points.Affected if Tabs exist that contain or accept unsanitized user input that could be exploited
If the WP Tabs plugin is active at version 2.2.0 or lower and contains tabs with user-supplied content, the environment is affected by this stored XSS vulnerability.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate WP Tabs plugin to a version beyond 2.2.0 which contains the fix for proper input sanitization. If immediate update is not possible, restrict administrative access and audit existing content for malicious script injections.
Fix this in Wp Tabs
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2023-52124 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-52124 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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