dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-49986

MEDIUM · 5.3 CVSS v3.1 Published 2025-06-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 thanhtungtnt Video List Manager video-list-manager allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Video List Manager: from n/a through <= 1.7.

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

The thanhtungtnt Video List Manager plugin (versions up to 1.7) contains a missing authorization vulnerability where certain functionality is not properly constrained by access control lists (ACLs). This broken access control issue allows users to access functionality they should not have permissions for, likely due to missing capability checks or privilege validation on sensitive operations.

MitigationImplement proper authorization and capability checks on all sensitive functions within the plugin, ensuring that only users with appropriate privileges can access protected functionality. All AJAX handlers and admin pages should verify user permissions before executing any operations.

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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Identify if the Video List Manager plugin is installed
    Access your WordPress admin dashboard, go to Plugins > Installed Plugins, and look for 'thanhtungtnt Video List Manager' or a similarly named video list plugin. Note the displayed version number.
    Affected if The plugin is installed and the version is 1.7 or lower (any version up to and including 1.7 is affected)
  2. Check plugin version via file inspection
    If accessible via file manager or FTP, navigate to wp-content/plugins/ and locate the plugin folder (typically named based on the developer name). Open the main plugin PHP file and read the Version header in the plugin comment block.
    Affected if The version read from the file is 1.7 or lower
  3. Test AJAX endpoint accessibility
    Using a tool like Burp Suite or curl, send a request to a typical WordPress AJAX endpoint (such as /wp-admin/admin-ajax.php) with an action parameter related to video management (e.g., actions involving save, delete, update, or manage). Send the request while logged in as a low-privilege user (subscriber or contributor) without admin capabilities.
    Affected if The AJAX action executes successfully and returns data or performs operations that should require administrator privileges
  4. Verify admin page access controls
    Navigate to the plugin admin menu pages while logged in as a user WITHOUT administrator role. Attempt to access any settings, management, or configuration pages provided by the plugin.
    Affected if Pages or sensitive functions are accessible and functional without proper capability checks
  5. Inspect plugin source for capability checks
    If you have file access, examine the main plugin PHP files for function calls like current_user_can(), check_admin_referer(), or wp_verify_nonce(). Search for AJAX handler registrations (add_action calls with wp_ajax_) and verify whether each includes a capability check before executing sensitive operations.
    Affected if AJAX handlers or admin page callbacks lack current_user_can() calls or other authorization validations

You are affected if the Video List Manager plugin (thanhtungtnt) is installed at version 1.7 or lower and sensitive functionality is accessible to users lacking administrative privileges.

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

Implement proper authorization and capability checks on all sensitive functions within the plugin, ensuring that only users with appropriate privileges can access protected functionality. All AJAX handlers and admin pages should verify user permissions before executing any operations.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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