dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-48750

MEDIUM · 5.3 CVSS v3.1 Published 2024-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 voidthemes Void Elementor Post Grid Addon for Elementor Page builder void-elementor-post-grid-addon-for-elementor-page-builder allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Void Elementor Post Grid Addon for Elementor Page builder: from n/a through <= 2.1.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 vulnerability in the Void Elementor Post Grid Addon where the plugin fails to properly enforce access control checks. This allows authenticated users (or potentially unauthenticated users depending on the specific endpoint) to access functionality or data they should not have permission to access due to incorrectly configured security levels.

MitigationImplement proper capability checks and authorization validation on all sensitive functions and data endpoints within the plugin, ensuring users have appropriate permissions before allowing access to restricted features.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 Void Elementor Post Grid Addon is installed
    Navigate to WordPress admin dashboard > Plugins and look for 'Void Elementor Post Grid Addon' in the installed plugins list; note its activation status and version number if displayed
    Affected if the plugin is installed and active on the WordPress site
  2. Identify plugin version from plugin files
    Access the plugin directory via file manager or FTP (typically /wp-content/plugins/void-elementor-post-grid-addon/), open the main plugin PHP file and locate the Version header in the plugin comment block
    Affected if the installed version cannot be determined or is older than any patched version released by the vendor
  3. Check for exposed AJAX endpoints
    Review plugin PHP files for wp_ajax_ and wp_ajax_nopriv_ action hooks; use a grep search for 'add_action.*wp_ajax' within the plugin directory to identify callable AJAX actions
    Affected if the plugin registers AJAX endpoints that do not include current_user_can() or capability checks before processing requests
  4. Inspect for vulnerable REST API routes
    Search plugin files for register_rest_route calls; examine if these routes implement permission_callback functions that validate user capabilities
    Affected if the plugin exposes REST API endpoints without proper permission_callback validation
  5. Review public query variables and parameters
    Examine plugin code for $_GET, $_POST, or $_REQUEST usage that processes input without capability verification; look for functions that output post grid data publicly
    Affected if the plugin accepts parameters without verifying user roles before returning sensitive data or performing actions

A site is affected if the Void Elementor Post Grid Addon plugin is installed and exposes functionality (AJAX actions, REST routes, or query handlers) that lacks proper capability checks and allows unauthorized access to restricted features or data.

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 on all sensitive functions and data endpoints within the plugin, ensuring users have appropriate permissions before allowing access to restricted features.

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-48750 — 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-2023-48750 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