dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-1631

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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
The Feeds for YouTube (YouTube video, channel, and gallery plugin) WordPress plugin before 2.6.4 is vulnerable to unauthorized modification of the Feeds for YouTube (YouTube video, channel, and gallery plugin) WordPress plugin before 2.6.4's license key due to a missing capability check on the 'actions' function. This makes it possible for subscribers and above delete the license key.

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

The Feeds for YouTube WordPress plugin before version 2.6.4 lacks a capability check on an 'actions' function, allowing authenticated users with subscriber-level permissions or higher to delete the plugin's license key via an insecure direct object reference. This is a Broken Access Control vulnerability where the function assumes the user has elevated privileges without verifying them.

MitigationUpdate the Feeds for YouTube plugin to version 2.6.4 or later, which should include proper capability checks. As a temporary workaround, restrict subscriber account creation until the patch is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

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 Feeds for YouTube plugin is installed
    Navigate to WordPress admin dashboard > Plugins and look for 'Feeds for YouTube' in the installed plugins list
    Affected if The plugin is installed and appears in the plugins list
  2. Check the installed plugin version
    In the Plugins page, click on the plugin name or view details to see the version number displayed
    Affected if The installed version is earlier than 2.6.4 (e.g., 2.6.3, 2.6.2, etc.)
  3. Identify if subscriber or higher-privilege user accounts exist
    Go to Users > All Users in the WordPress admin and review the role column for accounts with Subscriber, Contributor, Author, Editor, or Administrator roles
    Affected if There is at least one user account with Subscriber role or higher who could potentially trigger the vulnerable function
  4. Verify the license key configuration exists
    Navigate to the plugin settings page (usually under Settings > Feeds for YouTube or a dedicated YouTube Feeds menu item) and check if a license key is currently saved/activated
    Affected if A license key is saved in the plugin settings, as this is the object that can be deleted via the vulnerable function

You are affected if the Feeds for YouTube plugin version is below 2.6.4 AND you have user accounts with subscriber-level permissions or higher, since the missing capability check allows any such authenticated user to delete the license key.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Feeds for YouTube plugin to version 2.6.4 or later, which should include proper capability checks. As a temporary workaround, restrict subscriber account creation until the patch is applied.

Recommended fix High confidence

2.6.4

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Feeds for YouTube' plugin in the list
  4. Check the current version number displayed under the plugin name
  5. If the installed version is below 2.6.4, click 'Update Now' or 'Update' button for the plugin
  6. Wait for the update to complete and verify the new version number is 2.6.4
  7. Confirm the license key functionality works correctly after the update

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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