dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-68085

MEDIUM · 5.4 CVSS v3.1 Published 2025-12-16
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 Buttoner for Elementor buttoner-elementor allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Buttoner for Elementor: from n/a through <= 1.0.6.

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 Buttoner for Elementor WordPress plugin allows authenticated users to access functionality beyond their privilege level due to incorrectly configured access control security levels. The plugin fails to properly validate user capabilities before performing sensitive operations.

MitigationImplement proper capability checks and authorization verification for all sensitive functions, typically using WordPress current_user_can() or equivalent role-based access controls. Update to patched version when available.

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 Buttoner for Elementor plugin is installed
    Navigate to WordPress Admin > Plugins and look for 'Buttoner for Elementor' in the installed plugins list, or query the database: SELECT * FROM wp_options WHERE option_name = 'active_plugins'
    Affected if Buttoner for Elementor appears in the active plugins list
  2. Identify the installed plugin version
    Check the plugin header in wp-content/plugins/buttoner-for-elementor/buttoner-for-elementor.php for the 'Version:' field, or look in WordPress Admin > Plugins > Buttoner for Elementor details
    Affected if The version number matches or falls within any known affected version range (compare to vendor security advisory)
  3. Test for privilege escalation via plugin functions
    Using a low-privilege user account (subscriber level), attempt to access plugin admin functions or trigger AJAX actions related to button creation/management that should require administrator capabilities
    Affected if A subscriber-level user can successfully create, modify, or delete buttons or access plugin settings without receiving a 'You do not have permission' error
  4. Review user role capabilities for plugin operations
    Inspect the plugin source code (buttoner-for-elementor.php and includes/*.php) for current_user_can() or similar capability checks before sensitive operations like saving button configurations, exporting settings, or modifying plugin data
    Affected if Sensitive functions lack proper current_user_can() capability validation or accept any authenticated user regardless of role
  5. Check AJAX endpoints for authorization
    Examine wp-admin/admin-ajax.php calls made by the plugin (check console/network tab when using the plugin, or review PHP files for wp_ajax_ hooks) and test with a low-privilege account
    Affected if AJAX actions registered by the plugin accept requests from non-administrator users without verifying capabilities

The environment is affected if the Buttoner for Elementor plugin is installed and low-privilege authenticated users can access administrative or sensitive plugin functions that should require higher capabilities.

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 verification for all sensitive functions, typically using WordPress current_user_can() or equivalent role-based access controls. Update to patched version when available.

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