dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-66160

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

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 Graphist for Elementor WordPress plugin. The plugin fails to properly enforce access control security levels, allowing lower-privileged users to potentially access or manipulate functionality intended for higher-privileged users.

MitigationImplement proper capability checks and role-based access control (RBAC) enforcement on all sensitive functions within the plugin. Update to the latest patched version once available and verify that nonce verification and user capability checks are correctly applied to all AJAX actions and front-end rendering logic.

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 plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Graphist for Elementor' or search for it. Alternatively, check the /wp-content/plugins/ directory for a folder named 'graphist-elementor' or similar.
    Affected if The Graphist for Elementor plugin appears in the installed plugins list
  2. Identify installed version
    In WordPress admin > Plugins > Installed Plugins, find the Graphist for Elementor plugin and note the version number displayed under the plugin name. Alternatively, check the plugin's main PHP file for a 'Version' header comment.
    Affected if A version number is displayed (any version is potentially affected since no fixed version range was provided)
  3. Check user role configuration
    Go to WordPress admin > Users > Roles (or use a role management plugin) to review which user roles have access to Graphist for Elementor features. Verify if low-privileged roles like Subscriber, Contributor, or Editor can access the plugin's admin panels or shortcodes.
    Affected if Users with Subscriber, Contributor, or Editor roles can access or modify Graphist for Elementor settings or functionality intended for Administrators
  4. Test unauthorized access to admin functions
    Log in as a low-privileged user (e.g., Subscriber) and attempt to access the Graphist for Elementor admin pages directly via URL (e.g., /wp-admin/admin.php?page=graphist-settings). Also check if the plugin's AJAX endpoints are accessible without proper capability checks by inspecting the plugin's JavaScript network requests.
    Affected if Low-privileged users can access admin pages, modify settings, or trigger AJAX actions that should require Administrator capabilities

A user is affected if the Graphist for Elementor plugin is installed and low-privileged users (below Administrator) can access or manipulate plugin functionality that should be restricted to higher-privileged roles.

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 role-based access control (RBAC) enforcement on all sensitive functions within the plugin. Update to the latest patched version once available and verify that nonce verification and user capability checks are correctly applied to all AJAX actions and front-end rendering logic.

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