dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-66135

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

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 Imager for Elementor WordPress plugin before version 2.0.5 contains a missing authorization vulnerability where the plugin fails to properly enforce access control checks on certain functionality. This allows authenticated users with limited privileges (such as subscribers or contributors) to access or modify resources that should be restricted to administrators or higher-privileged users due to incorrectly configured access control security levels.

MitigationUpgrade Imager for Elementor to version 2.0.5 or later which contains proper authorization controls. Until then, restrict user permissions to untrusted roles and monitor for unauthorized access attempts.

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 Imager for Elementor plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Imager for Elementor' in the list of installed plugins, or check the file system at /wp-content/plugins/imager-for-elementor/
    Affected if The plugin is not installed or has been removed entirely (not affected)
  2. Identify the installed plugin version
    In WordPress admin > Plugins > Installed Plugins, find Imager for Elementor and read the version number displayed beneath the plugin name; alternatively, open /wp-content/plugins/imager-for-elementor/readme.txt and locate the 'Stable tag' or 'Version' entry in the file header
    Affected if The version displayed is anything before 2.0.5 (e.g., 2.0.4, 2.0.3, 1.x.x)
  3. Confirm low-privileged user roles exist
    In WordPress admin > Users > Roles, verify if roles such as Subscriber, Contributor, or Author exist and are actively assigned to user accounts; these roles have limited capabilities that should not have access to administrative functions
    Affected if Any user accounts with Subscriber, Contributor, or similar low-privilege roles are present in the system
  4. Check user role permissions configuration
    In WordPress admin > Imager for Elementor settings (or similar plugin settings page if accessible), look for any permission-related options that may control which user roles can access image manipulation or upload features
    Affected if Settings allow Subscriber or Contributor roles to access administrative-level image operations (vulnerability is exploitable)
  5. Audit recently created or modified media
    In WordPress admin > Media Library, review recent image uploads or modifications, particularly those submitted by users with Subscriber or Contributor roles, to identify potential unauthorized administrative actions
    Affected if Low-privilege users have created or modified images/attachments that would normally require administrator access

A user is affected if the Imager for Elementor plugin version is below 2.0.5 AND there are subscriber or contributor role accounts present in the WordPress installation that could potentially exploit the missing authorization controls.

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

Upgrade Imager for Elementor to version 2.0.5 or later which contains proper authorization controls. Until then, restrict user permissions to untrusted roles and monitor for unauthorized access attempts.

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-66135 — 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-66135 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