dbcve.org
My Youtube ChannelWordPress extension · Urosevic

CVE-2023-25987

HIGH · 8.8 CVSS v3.1 Published 2023-11-22
Fix available
A fix is available. Upgrade to 3.23.4 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 Aleksandar Urošević My YouTube Channel plugin <= 3.23.3 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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the My YouTube Channel WordPress plugin allows attackers to induce authenticated administrators to perform unintended actions by tricking their browsers into sending malicious requests to the vulnerable plugin, exploiting the lack of proper CSRF token validation on state-changing operations.

MitigationImplement anti-CSRF tokens (nonces) for all state-changing operations, validate the Referer/Origin headers, and set SameSite attribute on authentication cookies to prevent cross-site request forgery attacks.

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
My Youtube ChannelWordPress extension
Affected:< 3.23.4

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. Confirm plugin installation
    Access WordPress admin plugins page or check /wp-content/plugins/ directory for 'my-youtube-channel' or 'urosevic-youtube-channel' folder
    Affected if Plugin folder exists in the WordPress plugins directory
  2. Identify installed version
    Check plugin main file header in /wp-content/plugins/[plugin-folder]/my-youtube-channel.php for 'Version:' comment, or view plugin details in WordPress admin Plugins page
    Affected if Version number is lower than 3.23.4 (e.g., 3.23.3, 3.22.0, etc.)
  3. Identify exposed admin endpoints
    Check plugin PHP files for action hooks handling form submissions (look for 'admin_post_', 'admin-ajax.php', or form handlers in admin settings pages)
    Affected if Plugin has settings pages or forms that perform state-changing operations (saving options, updating channel data, etc.)
  4. Verify CSRF protection presence
    Examine plugin PHP code for nonce validation: search for 'wp_verify_nonce', 'check_admin_referer', or 'check_ajax_referer' in files handling form submissions
    Affected if State-changing functions lack nonce verification or use it incorrectly (e.g., nonce present but not validated before processing)
  5. Check for Referer/Origin header validation
    Search plugin code for '$_SERVER[HTTP_REFERER]' or '$_SERVER[HTTP_ORIGIN]' validation in admin request handlers
    Affected if No server header validation is performed before executing state-changing operations

User is affected if My YouTube Channel plugin version is below 3.23.4 and the plugin contains admin-facing forms or AJAX endpoints that modify settings without proper nonce or Referer validation.

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.23.4 or later
Fixed in 3.23.4
Interim mitigation

Implement anti-CSRF tokens (nonces) for all state-changing operations, validate the Referer/Origin headers, and set SameSite attribute on authentication cookies to prevent cross-site request forgery attacks.

Recommended fix High confidence

3.23.4

  1. Backup your WordPress site before making any changes
  2. Navigate to WordPress admin dashboard > Plugins
  3. Find 'My YouTube Channel' plugin in the installed plugins list
  4. Check if the current version is below 3.23.4
  5. If update available, click 'Update Now' to upgrade to version 3.23.4 or later
  6. Alternatively, navigate to Plugins > Add New > Upload and upload the latest version from wordpress.org
  7. Verify the plugin updated successfully by checking the version number
  8. Test the YouTube channel functionality to ensure the plugin still works correctly after the update

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

Fix this in My Youtube Channel 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-25987 — 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-25987 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