dbcve.org
Video GalleryWordPress extension · Yotuwp

CVE-2022-35726

CRITICAL · 9.8 CVSS v3.1 Published 2022-08-23
Fix available
A fix is available. Upgrade to 1.3.5 or later.
See remediation →
100/100
Remediation priority · Urgent
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 Authentication vulnerability in yotuwp Video Gallery plugin <= 1.3.4.5 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 confidence

Broken Authentication vulnerability in the yotuwp Video Gallery WordPress plugin versions 1.3.4.5 and earlier allows attackers to bypass authentication mechanisms. The specific attack vector and authentication weaknesses are not detailed in available sources, but the critical CVSS 9.8 score indicates severe impact potentially including full administrative account compromise.

MitigationUpdate the yotuwp Video Gallery plugin to the latest available version beyond 1.3.4.5. If no update is available, consider removing the plugin until a patch is released, and audit administrator accounts for unauthorized access.

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
Video GalleryWordPress extension
Affected:< 1.3.5

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Check installed Yotuwp Video Gallery plugin version
    In WordPress admin dashboard, go to Plugins > Installed Plugins, locate 'Yotuwp Video Gallery' and read the version number displayed beneath the plugin name. Alternatively, inspect the plugin main file header via file manager or FTP at /wp-content/plugins/yotuwp-video-gallery/yotuwp.php and look for 'Version:' in the file header comments.
    Affected if The installed version is 1.3.4.5 or any version number lower than 1.3.5.
  2. Verify if Yotuwp plugin is currently active
    In WordPress admin, go to Plugins > Installed Plugins and check if Yotuwp Video Gallery shows an 'Active' status link under the plugin name. Or query the wp_options table for option_name = 'active_plugins' and check if 'yotuwp-video-gallery/yotuwp.php' appears in the serialized active plugins list.
    Affected if The plugin is installed AND active (the vulnerability only applies to active plugin installations).
  3. Inspect administrator-level user accounts for anomalies
    In WordPress admin, go to Users > All Users and review all accounts with Administrator role. Look for unfamiliar usernames, unexpected email addresses, or accounts you did not create. Cross-reference creation dates with when the plugin may have been exposed. Alternatively, query wp_users and wp_usermeta tables directly to list all users with wp_capabilities containing 'administrator'.
    Affected if There are administrator accounts you did not create, or administrator accounts with suspicious usernames/email addresses.
  4. Review recent user registration activity
    Check the wp_users table for recently created accounts by querying for user_registered dates after the plugin version was first installed. Also review wp_options for the 'default_role' setting and any new user auto-registration settings that may have been changed.
    Affected if New user accounts were created during the period when the vulnerable plugin version was active, especially administrator-level accounts.

You are affected if the Yotuwp Video Gallery plugin version is 1.3.4.5 or lower AND the plugin is currently active in your WordPress installation.

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

Update the yotuwp Video Gallery plugin to the latest available version beyond 1.3.4.5. If no update is available, consider removing the plugin until a patch is released, and audit administrator accounts for unauthorized access.

Recommended fix High confidence

yotuwp Video Gallery version 1.3.5

  1. Back up your WordPress site before making any changes
  2. Navigate to the WordPress admin dashboard > Plugins > Installed Plugins
  3. Find the 'Video Gallery - yotuwp' plugin
  4. Click 'Update now' if an update is available, or manually upload version 1.3.5 from wordpress.org if the automatic update is not showing
  5. Verify the plugin is now running version 1.3.5 or later
  6. Test that the video gallery functionality is working correctly

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

Fix this in Video Gallery Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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