dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-66137

MEDIUM · 5.4 CVSS v3.1 Published 2026-01-22
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 Searcher for Elementor searcher-elementor allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Searcher for Elementor: from n/a through <= 1.0.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

Missing Authorization vulnerability in the Searcher for Elementor plugin allows unauthenticated or improperly authenticated users to access functionality that should be restricted by access control checks. The plugin fails to properly verify user capabilities or roles before allowing access to certain operations, allowing exploitation of incorrectly configured access control security levels.

MitigationImplement proper capability checks and authorization validation on all sensitive functions and AJAX endpoints within the plugin, ensuring that only users with appropriate permissions can access restricted functionality.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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. Confirm Searcher for Elementor plugin is installed
    Navigate to WordPress admin > Plugins and verify the 'Searcher for Elementor' plugin appears in the installed plugins list
    Affected if The plugin is installed and active on the WordPress site
  2. Check installed plugin version
    In WordPress admin > Plugins > Searcher for Elementor, view the version number displayed beneath the plugin name. Compare this to the affected version ranges if documented by the vendor.
    Affected if The installed version falls within an affected range that lacks the authorization fix
  3. Identify exposed AJAX endpoints
    Examine the plugin's PHP files for wp_ajax_ and wp_ajax_nopriv_ action hooks. Common paths: wp-content/plugins/searcher-for-elementor/includes/ or similar. Use grep: grep -r 'add_action.*wp_ajax' within the plugin directory.
    Affected if AJAX endpoints are registered with wp_ajax_nopriv_ hooks allowing unauthenticated access to sensitive functionality
  4. Test authorization on sensitive functions
    Make an unauthenticated HTTP request to identified AJAX endpoints (e.g., via curl or browser DevTools) to see if the plugin returns data or performs actions without requiring authentication
    Affected if The plugin responds to unauthenticated requests with successful data or performs actions that should require elevated privileges
  5. Review capability checks in plugin code
    Inspect PHP functions handling sensitive operations. Search for current_user_can, check_admin_referer, and capability verification. Use grep: grep -r 'current_user_can' within the plugin directory to locate authorization logic.
    Affected if Sensitive functions lack proper current_user_can() checks or capability validation before executing privileged operations

A site is affected if the Searcher for Elementor plugin is installed with a version that lacks proper capability checks on AJAX endpoints or sensitive functions, allowing unauthenticated or unauthorized access to restricted functionality.

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 capability checks and authorization validation on all sensitive functions and AJAX endpoints within the plugin, ensuring that only users with appropriate permissions can access restricted functionality.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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