dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-25988

HIGH · 7.5 CVSS v3.1 Published 2024-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Missing Authorization vulnerability in Video Gallery by Total-Soft Video Gallery – YouTube Gallery allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Video Gallery – YouTube Gallery: from n/a through 1.7.6.

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

A Missing Authorization vulnerability exists in the Video Gallery plugin where access control security levels are incorrectly configured, allowing unauthorized users to access restricted functionality. The plugin fails to properly validate user permissions before allowing access to certain operations.

MitigationImplement proper role-based authorization checks and access control validation throughout the plugin to ensure users can only access functionality permitted by their assigned security level.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Identify Video Gallery plugin installation
    Check your CMS or web application for any installed Video Gallery plugin. Common locations: WordPress plugins directory, Joomla extensions, Drupal modules, or custom plugin folders. Look for files or modules named 'video-gallery', 'gallery-video', or similar.
    Affected if A Video Gallery plugin is installed and the specific version matches or precedes the fixed release.
  2. Determine plugin version
    Locate the plugin's version file (typically version.php, readme.txt, or composer.json in the plugin directory). Compare the installed version number against any publicly disclosed fixed version for CVE-2023-25988.
    Affected if The installed version is the same as or earlier than the vulnerable version range.
  3. Review access control configuration
    Examine the plugin's configuration files and admin settings panel. Look for permission settings, role definitions, or access level controls that govern who can upload, edit, delete, or view video content.
    Affected if Access control settings are present but do not enforce proper role-based validation or allow unauthorized access to administrative functions.
  4. Test for unauthorized access to restricted functions
    Attempt to access plugin administrative features (such as video upload, playlist management, or settings modification) using a low-privilege or unauthenticated account. Observe whether the plugin grants access without proper authorization checks.
    Affected if The plugin permits access to restricted functionality without validating the user's security level or permissions.
  5. Inspect authentication hooks and callbacks
    Review the plugin's PHP or source code files for authorization checks before critical functions. Look for missing capability checks, nonce verification, or permission validation in AJAX handlers or admin action callbacks.
    Affected if The code lacks proper authorization checks (such as current_user_can(), check_admin_referer(), or role validation) before executing privileged operations.

Your environment is affected if a Video Gallery plugin is installed with a vulnerable version AND access control misconfigurations allow unauthorized users to access restricted functionality without proper permission 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper role-based authorization checks and access control validation throughout the plugin to ensure users can only access functionality permitted by their assigned security level.

Recommended fix Moderate confidence

Latest available version of Video Gallery by Total-Soft (YouTube Gallery) - check WordPress plugin repository for current release

  1. 1. Update the Video Gallery by Total-Soft plugin to the latest available version from the WordPress plugin repository
  2. 2. After updating, verify that the plugin settings maintain correct access control configurations
  3. 3. Review user role capabilities to ensure only authorized users can access video gallery management features
  4. 4. Test the gallery functionality to confirm the authorization controls are working properly

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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