dbcve.org
Shortcode AddonsWordPress extension · Oxilab

CVE-2022-33970

HIGH · 7.2 CVSS v3.1 Published 2022-07-27
Fix available
A fix is available. Upgrade to 3.2.0 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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
Authenticated WordPress Options Change vulnerability in Biplob018 Shortcode Addons plugin <= 3.1.2 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 · high confidence

The Biplob018 Shortcode Addons plugin versions 3.1.2 and below allows authenticated users (with subscriber-level access or higher) to modify WordPress options due to missing capability checks and improper input validation in the shortcode functionality.

MitigationUpdate the Biplob018 Shortcode Addons plugin to a version newer than 3.1.2. If no patched version is available, remove the plugin entirely and seek an alternative.

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
Shortcode AddonsWordPress extension
Affected:< 3.2.0

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
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 checks

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

  1. Confirm plugin installation and version
    Navigate to WordPress admin > Plugins and locate the Shortcode Addons plugin (listed as Oxilab Shortcode Addons or Biplob018 Shortcode Addons). Note the installed version number displayed in the plugin list.
    Affected if The installed version is below 3.2.0 (for example, 3.1.2, 3.1.1, 3.0, etc.)
  2. Verify shortcode is registered
    Check the plugin source files (typically in wp-content/plugins/shortcode-addons or similar directory) for registered shortcodes using add_shortcode() function. Also test by inserting a known shortcode like [oxilab_shortcode] into a post and viewing the page.
    Affected if Any shortcode from this plugin is active on the site, regardless of whether it appears to function correctly
  3. Check for subscriber-level user accounts
    In WordPress admin, go to Users > All Users and review the list. Note whether any users exist with the Subscriber role (or any role that grants authenticated access).
    Affected if At least one user account with Subscriber, Contributor, Author, Editor, or Administrator role exists on the site
  4. Inspect plugin capability handling
    Examine the plugin PHP files for capability checks before option modification actions. Look for functions that modify wp_options and verify if current_user_can() or a capability check is present before the action.
    Affected if The plugin lacks capability checks before modifying WordPress options, allowing any authenticated user to alter settings

A user is affected if the Oxilab/Biplob018 Shortcode Addons plugin version is below 3.2.0 AND the plugin shortcode is active AND at least one authenticated user account exists on the WordPress site.

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

Update the Biplob018 Shortcode Addons plugin to a version newer than 3.1.2. If no patched version is available, remove the plugin entirely and seek an alternative.

Recommended fix High confidence

Shortcode Addons 3.2.0

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Shortcode Addons' by Biplob018 in the plugin list
  4. If an update is available, click 'Update Now' to update to version 3.2.0 or later
  5. Alternatively, go to Dashboard > Updates and select Shortcode Addons to update
  6. After updating, verify the plugin version shows 3.2.0 or higher under Plugins > Installed Plugins

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

Fix this in Shortcode Addons Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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