dbcve.org
Mdc Youtube DownloaderWordPress extension · Mdc Youtube Downloader Project

CVE-2025-23639

MEDIUM · 6.1 CVSS v3.1 Published 2025-01-16
Fix available
A fix is available. Upgrade to after 3.0.0 or later.
See remediation →
68/100
Remediation priority · Elevated
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 Nazmul Ahsan MDC YouTube Downloader mdc-youtube-downloader allows Stored XSS.This issue affects MDC YouTube Downloader: from n/a through <= 3.0.0.

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

CSRF vulnerability in the MDC YouTube Downloader WordPress plugin allows attackers to trick authenticated administrators into submitting malicious requests that inject persistent JavaScript (Stored XSS) into the application, which then executes when other users view the affected content.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing form actions and verify the Origin/Referer headers on POST requests to prevent forged requests from injecting malicious scripts.

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
Mdc Youtube DownloaderWordPress extension
Affected:<= 3.0.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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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
    In WordPress admin, go to Plugins > Installed Plugins and locate 'MDC YouTube Downloader' or 'Mdc Youtube Downloader'. Check the version number displayed. Compare it to the affected range: <= 3.0.0
    Affected if The installed version is 3.0.0 or lower
  2. Identify admin forms that handle user input
    Examine the plugin's PHP files in wp-content/plugins for form handlers that accept user input (typically $_POST or $_REQUEST). Look for settings pages, download options, or any input fields that save data to the database
    Affected if The plugin contains admin forms that process and store user-submitted data without apparent nonce verification
  3. Verify nonce/token presence in form handlers
    Search the plugin code forwp_nonce_field, wp_nonce_url, check_admin_referer, or verify_nonce functions. Check if these are present and properly used on forms that modify plugin settings or save content
    Affected if State-changing forms (POST requests) lack nonce verification or use nonce checks incorrectly (e.g., nonce not verified before processing)
  4. Check input sanitization on stored data
    Examine how the plugin handles and outputs data: look for functions like sanitize_text_field, esc_html, esc_attr, or similar sanitization when saving to and reading from the database. Identify where stored data is output to admin pages or front-end
    Affected if Data submitted through admin forms is stored and displayed without proper sanitization, allowing script injection
  5. Test for CSRF vulnerability
    Create a malicious HTML page that submits a form to the plugin's admin endpoint (e.g., settings page URL). Submit the form without a valid nonce. If the action completes without rejection, the plugin lacks CSRF protection
    Affected if Form submissions succeed without valid anti-CSRF tokens, allowing attackers to forge requests on behalf of authenticated administrators

If the plugin version is 3.0.0 or lower AND admin forms lack proper nonce verification AND submitted data is not sanitized before storage, the environment is vulnerable to CVE-2025-23639 CSRF-to-Stored-XSS attacks.

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.

From vendor data
Upgrade available Upgrade to a release after 3.0.0
Interim mitigation

Implement anti-CSRF tokens (nonces) on all state-changing form actions and verify the Origin/Referer headers on POST requests to prevent forged requests from injecting malicious scripts.

Fix this in Mdc Youtube Downloader Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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