dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-25333

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-19
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 peregrinethemes Shopwell shopwell allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Shopwell: from n/a through <= 1.0.11.

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 Shopwell theme/plugin by peregrinethemes that allows attackers to exploit incorrectly configured access control security levels. The vulnerability stems from the application failing to properly verify user permissions before allowing access to certain functionality or data, potentially allowing unauthorized users to perform actions or access resources they should not have permission to access.

MitigationImplement proper authorization checks throughout the application, particularly on sensitive functionality and data access points, ensuring all user roles are validated against defined security levels before granting 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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Identify if Shopwell theme/plugin is installed
    Check your WordPress installation's themes and plugins directory for a theme or plugin named 'Shopwell' by 'peregrinethemes'. In WordPress admin, go to Appearance > Themes or Plugins to list installed items.
    Affected if Shopwell theme or plugin by peregrinethemes is present in the installation
  2. Determine the installed version
    If Shopwell is installed, locate its version number. For themes, check style.css header comments or the theme's main file. For plugins, check the main plugin PHP file header or the Plugins admin page.
    Affected if A version of Shopwell exists but no specific version range was provided for comparison; compare to any advisories from the vendor
  3. Inspect authorization logic in sensitive files
    Examine PHP files within the Shopwell theme/plugin directory for access control checks. Look for functions that handle user roles, capabilities, or permission verification. Search for patterns like 'current_user_can', 'wp_get_current_user', or role checks. Identify if sensitive functions (settings, user data, admin actions) have proper authorization gates.
    Affected if Sensitive functions or data access points lack proper permission checks (e.g., missing current_user_can() calls before executing actions)
  4. Test access to privileged endpoints
    If you have access to the site, attempt to access admin/dashboard areas or sensitive functionality with a low-privilege user account (subscriber, guest). Observe whether the application returns protected content or allows actions without rejecting the request based on insufficient permissions.
    Affected if A user with limited or no privileges can access resources or perform actions that should require higher authorization levels
  5. Review role and capability configurations
    Check the theme/plugin code for how it defines or handles user roles and capabilities. Look for any hardcoded role assignments, capability checks that are commented out, or conditional logic that skips authorization under certain conditions.
    Affected if The application assigns elevated roles/capabilities incorrectly or bypasses role-based access control logic

A user is affected if the Shopwell theme/plugin by peregrinethemes is installed and sensitive functionality or data can be accessed or modified by unauthorized users due to missing permission 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

Implement proper authorization checks throughout the application, particularly on sensitive functionality and data access points, ensuring all user roles are validated against defined security levels before granting access.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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