dbcve.org
Youtube Video GalleryWordPress extension · Emarketdesign

CVE-2023-40558

HIGH · 8.8 CVSS v3.1 Published 2023-10-03
Fix available
A fix is available. Upgrade to 3.3.6 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in eMarket Design YouTube Video Gallery by YouTube Showcase plugin <= 3.3.5 versions.

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

Cross-Site Request Forgery (CSRF) vulnerability in the YouTube Showcase WordPress plugin versions 3.3.5 and below. The plugin lacks proper anti-CSRF token validation on state-changing operations, allowing attackers to trick authenticated administrators into unknowingly executing unintended actions such as modifying gallery settings or manipulating video entries.

MitigationUpgrade to the latest version of the YouTube Showcase plugin (currently unavailable from description, check vendor advisories). Additionally, implement anti-CSRF tokens (synchronizer token pattern) for all form submissions and AJAX requests, and validate Origin/Referer headers on the server side.

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

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Locate the YouTube Showcase plugin installation
    Check the WordPress plugins directory at wp-content/plugins/ for a folder named 'youtube-showcase', 'youtube-video-gallery', or similar Emarketdesign YouTube related plugin directories. Also check the WordPress admin under Plugins > Installed Plugins for 'YouTube Showcase' or 'Emarketdesign Youtube Video Gallery'.
    Affected if The plugin is not found in either location, indicating it is not installed.
  2. Identify the installed version number
    If the plugin is found, open the main plugin PHP file (usually named similar to the folder) and look for the 'Version' header in the plugin comment block. Alternatively, check the plugin's readme.txt file for the version number.
    Affected if The version is 3.3.5 or below, placing it within the affected range of < 3.3.6.
  3. Confirm the plugin is active
    Log into WordPress admin and check if the YouTube Showcase plugin appears in the list of active plugins, or query the wp_options table for the option_name containing 'active_plugins'.
    Affected if The plugin is active and the version is 3.3.5 or below.
  4. Inspect plugin forms for CSRF protection
    Navigate to the YouTube Showcase settings page in WordPress admin. View the HTML source of any form (settings, gallery configuration, video entry forms). Check if each form contains a hidden input field with a name like 'wpnonce', '_wpnonce', 'nonce', or similar security token.
    Affected if Forms lack hidden nonce token fields, indicating the anti-CSRF mechanism may be missing.
  5. Verify nonce validation in plugin code
    If you have file access, examine the plugin's main PHP files (particularly those handling form submissions and AJAX requests). Search for calls to 'wp_verify_nonce', 'check_ajax_referer', or similar nonce validation functions within the handlers that process state-changing operations.
    Affected if No nonce validation calls are found in the form processing code, confirming the vulnerability exists.

A user is affected if the Emarketdesign Youtube Video Gallery plugin is installed, active, and running version 3.3.5 or below without nonce token validation on its forms.

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.3.6 or later
Fixed in 3.3.6
Interim mitigation

Upgrade to the latest version of the YouTube Showcase plugin (currently unavailable from description, check vendor advisories). Additionally, implement anti-CSRF tokens (synchronizer token pattern) for all form submissions and AJAX requests, and validate Origin/Referer headers on the server side.

Recommended fix High confidence

3.3.6

  1. Upgrade the YouTube Video Gallery (YouTube Showcase) plugin to version 3.3.6 or later

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

Fix this in Youtube Video Gallery Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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