dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-57405

HIGH · 7.1 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click 5 weeks old

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 themehunk Open Shop open-shop allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Open Shop: from n/a through <= 1.7.1.

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 · low confidence

This is a Missing Authorization vulnerability in the Open Shop WordPress theme by themehunk. The theme has incorrectly configured access control security levels, allowing unauthenticated or improperly authenticated users to access functionality or data that should be restricted. The specific attack vector and affected endpoints are not detailed in the available information.

MitigationUpdate to the latest version of the Open Shop theme when a patch becomes available. In the interim, review theme settings and restrict access to sensitive areas through web server-level authentication or WordPress capability checks if feasible.

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
High

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

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. Identify Open Shop theme installation and version
    In WordPress admin dashboard, go to Appearance > Themes to confirm Open Shop theme is active. Note the installed version from the theme details. Compare this version against any known vulnerable versions if documented elsewhere.
    Affected if Open Shop theme by themehunk is active and the version is prior to any patched release.
  2. Inspect theme admin access controls
    Navigate to theme settings pages (Appearance > Customize > Open Shop Options or similar). Attempt to access these pages while logged out or as a low-privilege user (subscriber). Check if the theme allows access without proper WordPress capability checks.
    Affected if Non-admin users or unauthenticated visitors can access theme configuration panels that should require administrator privileges.
  3. Review AJAX endpoints for authorization gaps
    Examine the theme directory for AJAX handlers (look for wp_ajax_ and wp_ajax_nopriv_ hooks in theme files). Check if functions accessible via these hooks enforce proper user authentication and capability checks before returning sensitive data or performing actions.
    Affected if AJAX endpoints registered with wp_ajax_nopriv_ or lacking current_user_can() checks return privileged data or allow privileged actions.
  4. Audit customizer and theme options exposure
    Access WordPress Customizer via /wp-admin/customize.php while logged out or as a subscriber-level user. Check if theme customizer controls load without proper authentication.
    Affected if Theme customizer settings are accessible without being logged in or without sufficient WordPress capabilities.
  5. Check file inclusion and execution points
    Review theme PHP files for functions that accept user input and could execute files or database operations. Verify these functions include capability checks like current_user_can() or is_user_logged_in() before proceeding.
    Affected if Theme functions process requests without verifying user identity or authorization level.

A user is affected if the Open Shop theme is active and unauthenticated or low-privilege users can access admin functions, theme settings, AJAX handlers, or customizer options that should require administrator-level WordPress 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

Update to the latest version of the Open Shop theme when a patch becomes available. In the interim, review theme settings and restrict access to sensitive areas through web server-level authentication or WordPress capability checks if feasible.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57405 — 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-57405 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