dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-24972

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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 Elated-Themes Elated Listing eltd-listing allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Elated Listing: from n/a through <= 1.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

Missing authorization vulnerability in the Elated Listing WordPress plugin allows attackers to exploit incorrectly configured access control security levels. Unauthenticated or low-privilege users can likely access functionality that should require higher privileges or admin authentication.

MitigationImplement proper authorization checks (e.g., current_user_can()) on all sensitive actions and admin pages within the plugin, ensuring all endpoints validate user capabilities before allowing access.

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 Elated Listing plugin is installed
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, or inspect /wp-content/plugins/ directory for 'elated-listing' folder. Alternatively, query the wp_options table for 'active_plugins' or check the plugin files directly.
    Affected if The Elated Listing plugin is present and active in the WordPress installation.
  2. Identify installed plugin version
    Check the plugin main file (usually elated-listing.php) for the 'Version' header comment, or look in the plugin readme.txt file. In WordPress admin, view plugin details to see the version number.
    Affected if A version of Elated Listing is installed. Since no specific version range was provided, any installed version may be affected.
  3. Inspect AJAX endpoints for authorization
    Examine the plugin PHP files for wp_ajax_ and wp_ajax_nopriv_ hooks. Check if these endpoints perform capability checks using current_user_can() or similar authorization functions before executing sensitive actions.
    Affected if AJAX endpoints exist without proper current_user_can() checks before processing requests.
  4. Check admin page access controls
    Review plugin PHP files for add_menu_page, add_submenu_page, or admin_init hooks. Verify that these pages or actions include capability verification (e.g., manage_options, edit_listings) before allowing access.
    Affected if Admin pages or menu items lack capability checks and are accessible to low-privilege or unauthenticated users.
  5. Test low-privilege user access
    Create or use a subscriber-level user account. Attempt to access plugin-related pages directly via URL or trigger AJAX actions that should require administrator privileges. Observe if requests succeed without authorization errors.
    Affected if Low-privilege or unauthenticated users can successfully execute actions that should require administrator capabilities.

The environment is affected if the Elated Listing plugin is installed and low-privilege or unauthenticated users can access admin functions or sensitive plugin actions without proper capability verification.

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 authorization checks (e.g., current_user_can()) on all sensitive actions and admin pages within the plugin, ensuring all endpoints validate user capabilities before allowing access.

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-2026-24972 — 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-2026-24972 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