Responsive TabsWordPress extension · Oxilab
CVE-2022-36375
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 · uneditedAuthenticated (high role user) WordPress Options Change vulnerability in Biplob Adhikari's Tabs plugin <= 3.6.0 at WordPress.
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 confidenceAuthenticated high-role user can modify WordPress options through the Tabs plugin version 3.6.0 or lower, potentially allowing privilege escalation or site configuration changes.
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 TabsWordPress extension
<= 3.6.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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check if Oxilab Responsive Tabs plugin is installedNavigate to WordPress admin > Plugins and look for 'Oxilab Responsive Tabs' or inspect the /wp-content/plugins/ directory for a folder containing 'responsive-tabs' or 'oxilab' in the nameAffected if The plugin appears in the installed plugins list or its folder exists in the wp-content/plugins directory
-
Verify the installed plugin versionIn WordPress admin > Plugins, click on the plugin details for Oxilab Responsive Tabs and read the version number displayed, or open the main plugin PHP file and look for the 'Version' header in the plugin comment blockAffected if The version number displayed is 3.6.0 or lower (e.g., 3.6.0, 3.5.9, 3.5.0, etc.)
-
Confirm authenticated user access existsNavigate to WordPress admin > Users and review the list of registered users, noting those with Administrator, Editor, or Author rolesAffected if Any user accounts exist with elevated roles (Administrator, Editor, or Author) who could potentially access the vulnerable functionality
-
Check plugin options functionalityLook for a menu item under the WordPress admin sidebar created by this plugin (often under 'Oxilab' or 'Tabs' menu), then access the plugin settings page where options can be modifiedAffected if The plugin settings page is accessible and allows modifying WordPress options (not just plugin-specific settings)
The environment is affected if Oxilab Responsive Tabs version 3.6.0 or lower is installed AND any authenticated user with Administrator, Editor, or Author role exists who could access the plugin's options modification functionality.
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 the Tabs plugin to a version higher than 3.6.0. If no update is available, remove the plugin or restrict administrative access to trusted personnel only.
Fix this in Responsive Tabs
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36375 — 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-2022-36375 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