dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-24984

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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
Missing Authorization vulnerability in Brecht Visual Link Preview visual-link-preview allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Visual Link Preview: from n/a through <= 2.2.9.

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

Missing Authorization vulnerability in the Visual Link Preview WordPress plugin allows exploiting incorrectly configured access control security levels. The plugin fails to properly validate user capabilities before performing privileged operations, potentially enabling lower-privileged or unauthenticated users to access sensitive functionality.

MitigationImplement proper WordPress capability checks (current_user_can) and nonce verification for all AJAX actions and admin functions. Audit all functions that modify data or access sensitive information to ensure they enforce appropriate authorization controls.

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installed plugin version
    Navigate to WordPress admin > Plugins > Visual Link Preview and note the version number, or run: wp plugin list --name='visual-link-preview' --format=table
    Affected if The installed version matches the vulnerable version range for this CVE (check against official vulnerability disclosure)
  2. Verify WordPress user role configuration
    In WordPress admin, go to Users > All Users and review the roles assigned to each user account. Note which users have Subscriber, Contributor, or Author roles versus Administrator
    Affected if Lower-privileged users (Subscriber, Contributor, Author) exist on the site and the plugin exposes functionality they should not access
  3. Inspect AJAX action handlers for capability checks
    Locate the plugin PHP files (typically in wp-content/plugins/visual-link-preview/) and search for 'add_action' calls with 'wp_ajax_' hook. Verify if each handler includes 'current_user_can()' or a capability check before processing
    Affected if AJAX handlers exist that lack 'current_user_can()' validation or capability checks before executing privileged operations
  4. Review admin function authorization
    Examine the plugin admin PHP files for functions that modify data or access sensitive information. Check if these functions verify user capabilities using current_user_can() or similar WordPress authorization functions
    Affected if Admin functions that handle sensitive operations are missing proper capability verification checks
  5. Check for nonce verification in AJAX calls
    Search the plugin source code for 'wp_ajax_' actions and verify if each includes nonce verification using 'check_ajax_referer' or 'wp_verify_nonce' before processing requests
    Affected if AJAX actions process requests without validating nonces, allowing potential request forgery
  6. Test unauthenticated access to plugin features
    Attempt to access plugin functionality directly via AJAX endpoints (usually /wp-admin/admin-ajax.php?action=visual_link_preview_*) while logged out or as a low-privilege user
    Affected if Unauthenticated or low-privileged users can successfully execute plugin functions that should require higher privileges

A user is affected if they have Visual Link Preview plugin installed and the installed version is within the vulnerable range, and the plugin code is missing capability checks (current_user_can) and nonce verification on its AJAX actions and admin functions.

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 WordPress capability checks (current_user_can) and nonce verification for all AJAX actions and admin functions. Audit all functions that modify data or access sensitive information to ensure they enforce appropriate authorization controls.

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-2026-24984 — 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-24984 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