dbcve.org
Custom Product Tabs For WoocommerceWordPress extension · Yikesinc

CVE-2022-28666

MEDIUM · 5.3 CVSS v3.1 Published 2022-07-21
Fix available
A fix is available. Upgrade to after 1.7.7 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Broken Access Control vulnerability in YIKES Inc. Custom Product Tabs for WooCommerce plugin <= 1.7.7 at WordPress leading to &yikes-the-content-toggle option update.

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

Broken Access Control vulnerability in YIKES Custom Product Tabs for WooCommerce plugin versions 1.7.7 and below allows unauthorized modification of the yikes-the-content-toggle WordPress option without proper capability checks, potentially enabling attackers to inject malicious content or alter plugin behavior.

MitigationUpdate the plugin to version 1.8.0 or later which patches the authorization flaw; if immediate update is not possible, audit recent option changes and restrict access to the vulnerable endpoint.

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
Custom Product Tabs For WoocommerceWordPress extension
Affected:<= 1.7.7

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
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Confirm plugin installation and version
    Locate the plugin directory (typically wp-content/plugins/yikes-inc-custom-product-tabs-for-woocommerce/) and check the main plugin file header or readme.txt for the version number
    Affected if The installed version is 1.7.7 or lower
  2. Identify the vulnerable option in database
    Query the wp_options table for the option_name 'yikes-the-content-toggle' using: SELECT * FROM wp_options WHERE option_name = 'yikes-the-content-toggle';
    Affected if The option exists and contains a value that could be modified
  3. Test option modifiability without authentication
    Send a POST request to the plugin's admin-ajax.php or settings endpoint modifying the yikes-the-content-toggle option without including authentication cookies or with a low-privilege user account
    Affected if The option value changes successfully without proper capability verification
  4. Check user role capability requirements
    Review the plugin source code (specifically the AJAX handler or form processor) for the capability check (should require 'manage_options' capability) when the yikes-the-content-toggle option is modified
    Affected if The code lacks a current_user_can() check for 'manage_options' or equivalent before updating the option

A user is affected if the YIKES Custom Product Tabs for WooCommerce plugin version 1.7.7 or below is installed and the yikes-the-content-toggle option can be modified by unauthenticated or unauthorized users.

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 a release after 1.7.7
Interim mitigation

Update the plugin to version 1.8.0 or later which patches the authorization flaw; if immediate update is not possible, audit recent option changes and restrict access to the vulnerable endpoint.

Recommended fix Moderate confidence

Custom Product Tabs For WooCommerce version 1.7.8 or later (latest available version)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Custom Product Tabs For WooCommerce' in the plugin list
  4. Check if an update is available and install the latest version
  5. Verify the plugin is functioning correctly after update

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

Fix this in Custom Product Tabs For Woocommerce Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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