dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2023-40200

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-11
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
Authorization bypass through User-Controlled key vulnerability in Essential Plugin WP Logo Showcase Responsive Slider and Carousel allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects WP Logo Showcase Responsive Slider and Carousel: from n/a through 3.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

Authorization bypass vulnerability in the WP Logo Showcase Responsive Slider and Carousel WordPress plugin allows unauthenticated or low-privilege attackers to access functionality or data that should require higher privileges. The vulnerability stems from the plugin using user-controlled input to make access control decisions without proper validation, resulting in incorrectly configured access control security levels.

MitigationUpdate to the latest version of the plugin if a patch is available. If no patch exists, disable the plugin or implement Web Application Firewall (WAF) rules to block requests exploiting the authorization bypass until a fix is released.

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. Verify the plugin is installed and get its version
    Log into WordPress admin, go to Plugins > Installed Plugins, find 'WP Logo Showcase Responsive Slider and Carousel' and note the version number displayed. Alternatively, check the main plugin file (usually in /wp-content/plugins/logo-showcase-with-carousel/ or similar) for the 'Version' header in the plugin comment block.
    Affected if The installed version is 3.6 or earlier
  2. Confirm the plugin is active
    In the WordPress admin Plugins page, verify the plugin shows as 'Active' rather than 'Inactive'. An inactive plugin with the vulnerability present may still be exploitable if the files remain on the server.
    Affected if The plugin is currently active on the site
  3. Check for exposed admin AJAX endpoints
    Examine the plugin's main PHP file for AJAX action hooks (add_action calls with 'wp_ajax_') that handle user-supplied parameters. Look for endpoints that accept IDs, keys, or other user-controlled values without verifying user capabilities using current_user_can() or similar authorization checks.
    Affected if AJAX endpoints exist that process user-supplied parameters without proper authorization validation
  4. Identify if non-admin users have access to plugin settings
    In WordPress admin, create a test subscriber or editor account, log in with those credentials, and attempt to access the plugin settings page (usually under Logos or a dedicated menu item). Also check if any shortcodes or public-facing features accept parameters that could reference admin-level data.
    Affected if Lower-privileged users can access plugin administrative functions or modify settings they should not be able to alter

If the plugin version is 3.6 or earlier and the plugin is active, the environment is likely affected by this authorization bypass vulnerability.

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 to the latest version of the plugin if a patch is available. If no patch exists, disable the plugin or implement Web Application Firewall (WAF) rules to block requests exploiting the authorization bypass until a fix is released.

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