Related Youtube VideosWordPress extension · Meomundo
CVE-2019-5980
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 · uneditedCross-site request forgery (CSRF) vulnerability in Related YouTube Videos versions prior to 1.9.9 allows remote attackers to hijack the authentication of administrators via unspecified vectors.
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 confidenceCSRF vulnerability in the Related YouTube Videos WordPress plugin versions prior to 1.9.9 allows remote attackers to hijack administrator authentication by tricking logged-in administrators into unknowingly submitting malicious requests, enabling unauthorized configuration changes or plugin actions.
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
Related Youtube VideosWordPress extension
< 1.9.9CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate the Related YouTube Videos plugin in WordPressLog into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Meomundo Related Youtube Videos' or 'Related YouTube Videos' in the list of installed plugins.Affected if The plugin is installed and appears in the WordPress plugins list.
-
Identify the installed plugin versionIn the plugins list, click on the plugin to view its details, or check the plugin header comment in the main plugin file (typically in /wp-content/plugins/related-youtube-videos/ or similar path). The version number is listed in the plugin metadata.Affected if The version number displayed is lower than 1.9.9 (e.g., 1.9.8, 1.9.7, 1.0.0, etc.).
-
Confirm the plugin is activeIn the WordPress admin under Plugins > Installed Plugins, verify whether the Related YouTube Videos plugin shows as 'Active' rather than 'Inactive' or 'Must Use'.Affected if The plugin is installed, active, and the version is below 1.9.9.
A WordPress site is affected if it has the Meomundo Related Youtube Videos plugin installed and active with a version number lower than 1.9.9.
Generated from the published advisory. Verify against your own configuration.
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 data1.9.9
Update the Related YouTube Videos plugin to version 1.9.9 or later which includes anti-CSRF token validation; until patched, administrators should avoid clicking untrusted links while logged into the WordPress admin panel.
Fix this in Related Youtube Videos
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2019-5980 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-5980 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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