dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-66149

MEDIUM · 5.4 CVSS v3.1 Published 2025-12-31
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
Missing Authorization vulnerability in merkulove UnGrabber ungrabber allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects UnGrabber: from n/a through <= 3.1.3.

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

This is a Missing Authorization (Broken Access Control) vulnerability in the merkulove UnGrabber WordPress plugin. The vulnerability allows unauthenticated or improperly authenticated users to access functionality or data that should be restricted, due to incorrectly configured access control security levels in versions up to and including 3.1.3.

MitigationUpdate UnGrabber to the latest version once available, or audit and add proper capability checks, nonce verification, and role-based access controls to all sensitive functions in the plugin.

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. Verify UnGrabber plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'ungrabber' or containing 'merkulove' and 'UnGrabber' in the plugin files.
    Affected if The UnGrabber plugin folder exists in the WordPress plugins directory.
  2. Identify installed version
    Open the main plugin file (ungrabber.php) or the plugin's readme.txt and locate the version number in the plugin header comment.
    Affected if The version number found is 3.1.3 or lower.
  3. Check plugin capabilities configuration
    Examine the plugin's main PHP file for capability checks on sensitive functions (look for 'capability', 'manage_options', 'add_menu_page', 'admin_menu' hooks). Verify if all admin functions have proper current_user_can() checks.
    Affected if Sensitive functions or AJAX handlers lack capability checks or use weak/inadequate capabilities that allow unauthenticated or low-privilege access.
  4. Inspect AJAX endpoints for authorization
    Search plugin files for wp_ajax_ and wp_ajax_nopriv_ hooks. Check if any sensitive actions are registered with wp_ajax_nopriv_ (which allows unauthenticated access) without proper authorization verification inside the callback.
    Affected if The plugin registers AJAX actions accessible to unauthenticated users (wp_ajax_nopriv_) without performing capability checks or nonce verification in the callback.

If UnGrabber version 3.1.3 or lower is installed AND sensitive functionality (AJAX endpoints, admin pages, or data export features) can be accessed by unauthenticated users without proper capability checks, the environment is affected by CVE-2025-66149.

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 UnGrabber to the latest version once available, or audit and add proper capability checks, nonce verification, and role-based access controls to all sensitive functions in the plugin.

Recommended fix Moderate confidence

Latest available version of UnGrabber (version higher than 3.1.3)

  1. 1. Log in to the WordPress admin dashboard where the UnGrabber plugin is installed
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the UnGrabber plugin by merkulove
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Verify the update completed successfully by checking the plugin version
  6. 6. Test that the UnGrabber functionality continues to work as expected after the update

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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