dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-66142

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 Comparimager for Elementor comparimager-elementor allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Comparimager for Elementor: from n/a through <= 1.0.1.

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 Comparimager Elementor plugin allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized users to access or perform actions that should be restricted to higher-privileged users.

MitigationImplement proper capability checks and authorization validation for all sensitive functions and AJAX actions within the plugin to ensure users have appropriate permissions before granting access.

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. Verify Comparimager Elementor plugin is installed
    Log in to WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'Comparimager' or 'Comparimager Elementor' in the list of active plugins.
    Affected if The plugin appears in the list of installed plugins, regardless of activation status
  2. Identify the installed plugin version
    In the WordPress plugins list, click on the plugin name or view the plugin files. The version number is typically displayed in the plugin header comment in the main PHP file (often named comparimager.php or similar).
    Affected if A version number is returned and can be compared to the affected version range for this CVE
  3. Check for publicly accessible AJAX actions
    Inspect the plugin directory (typically wp-content/plugins/comparimager-elementor/) for PHP files containing 'add_action("wp_ajax_' or 'wp_ajax_nopriv_' hooks. These indicate AJAX endpoints that may lack proper capability checks.
    Affected if AJAX actions exist that either lack nopriv checks or do not verify user capabilities before executing sensitive operations
  4. Review WordPress user roles and plugin capability settings
    Navigate to WordPress admin > Users > Roles (or use a role management plugin) to examine what roles have access to plugin features. Check if low-privileged roles (like Subscriber or Contributor) can access settings or actions intended for Administrators.
    Affected if Users with Subscriber, Contributor, or Editor roles can access admin-level plugin functions or settings that should require Administrator privileges
  5. Inspect plugin PHP files for missing capability checks
    Examine the main plugin PHP files for function calls that should verify permissions, such as 'current_user_can()' or 'wp_verify_nonce()' before executing sensitive operations like database writes, file operations, or settings changes.
    Affected if Sensitive functions are found without preceding capability or authorization validation checks

You are affected if the Comparimager Elementor plugin is installed and its version falls within the affected range, or if low-privileged users can access functions that should require higher-level permissions.

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 for all sensitive functions and AJAX actions within the plugin to ensure users have appropriate permissions before granting access.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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