Missing AuthorizationWeakness · CWE-862

CVE-2023-47661

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-02
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 Dragfy Dragfy Addons for Elementor allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Dragfy Addons for Elementor: from n/a through 1.0.2.

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 Dragfy Addons for Elementor plugin versions through 1.0.2 allows unauthorized users to access functionality that should require higher privilege levels due to incorrectly configured access control security levels.

MitigationUpdate Dragfy Addons for Elementor to a version beyond 1.0.2 that includes proper authorization checks, or implement role-based access control (RBAC) checks on affected endpoints if no update is 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
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

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 Dragfy Addons for Elementor is installed
    In WordPress admin, navigate to Plugins > Installed Plugins and locate 'Dragfy Addons for Elementor', or check the /wp-content/plugins/ directory for the plugin folder
    Affected if Plugin is present and active on the WordPress site
  2. Check installed version against 1.0.2
    View the plugin details in WordPress admin plugins list, or inspect the main plugin file (e.g., dragfy-addons-for-elementor.php) to find the 'Version' header
    Affected if Version is 1.0.2 or lower (any version 'through 1.0.2' is affected)
  3. Identify affected endpoints or AJAX actions
    Inspect plugin PHP files for action hooks (wp_ajax_*, wp_ajax_nopriv_*, admin_post_*) that handle sensitive operations; check for missing capability checks like 'manage_options' or current_user_can() before executing privileged actions
    Affected if Plugin exposes admin-level functions (settings, content modification, user data access) without proper capability verification or without requiring authentication
  4. Audit access control on plugin admin pages
    Access the WordPress admin and navigate to any Dragfy menu items; attempt to access plugin settings, add/edit functionality, or database operations without elevated privileges
    Affected if Low-privilege users (subscriber, contributor, or unauthenticated visitors) can access or modify plugin settings or perform actions that should require administrator-level permissions
  5. Verify if authorization checks exist in vulnerable code paths
    Search plugin source code for current_user_can(), check_admin_referer(), or nonce verification before sensitive operations; review AJAX handlers for nopriv callbacks that perform privileged actions
    Affected if Code lacks capability checks or nonce validation on functions that modify site data, user data, or plugin configurations

Your environment is affected if the Dragfy Addons for Elementor plugin is installed with version 1.0.2 or lower AND the plugin exposes administrative functions or endpoints that can be accessed by unauthorized or low-privilege users without proper authorization checks.

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

Update Dragfy Addons for Elementor to a version beyond 1.0.2 that includes proper authorization checks, or implement role-based access control (RBAC) checks on affected endpoints if no update is 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-2023-47661 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2023-47661 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