dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-57776

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 vowelweb VW Wedding vw-wedding allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects VW Wedding: from n/a through <= 1.3.7.

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 (Broken Access Control) vulnerability in the vowelweb VW Wedding plugin/theme (versions up to 1.3.7). The vulnerability allows attackers to exploit incorrectly configured access control security levels, potentially accessing sensitive functionality or data without proper authentication or authorization checks.

MitigationImplement proper authorization checks on all sensitive endpoints and functions within the VW Wedding plugin, ensuring that access control security levels are correctly configured and enforced for all user roles.

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

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

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 VW Wedding installation
    Check your WordPress site's wp-content/plugins or wp-content/themes directory for a folder named 'vw-wedding', 'vowelweb-vw-wedding', or similar naming patterns associated with the VW Wedding plugin/theme.
    Affected if The VW Wedding plugin or theme from vowelweb is found in the WordPress installation
  2. Check installed version
    Locate the main plugin file (typically index.php or the main PHP file in the plugin folder) and look for a version constant or comment (e.g., define('VW_WEDDING_VERSION', 'x.x.x'); or 'Version: x.x.x' in the file header).
    Affected if The version number is 1.3.7 or earlier, or no version is specified (meaning it could be an unpatched older release)
  3. Identify sensitive endpoints
    Search the plugin files for PHP files containing admin, dashboard, settings, user, or data-related functions. Look for action hooks (add_action) and callback functions that handle sensitive operations.
    Affected if The plugin contains admin or sensitive functionality that may lack authorization checks
  4. Test for missing authorization
    Attempt to access identified sensitive functions/endpoints directly via HTTP requests without providing authentication credentials or with a low-privilege user account. Check if the server returns expected data or allows actions without rejecting the request.
    Affected if Sensitive functionality is accessible without proper authentication or authorization validation
  5. Review access control configuration
    Examine the plugin code for proper capability checks (current_user_can, is_user_logged_in) or nonce validation on sensitive functions. Look for missing or insufficient access control logic before sensitive operations.
    Affected if Sensitive functions lack proper current_user_can() checks or nonce validation before executing privileged actions

If the VW Wedding plugin/theme version is 1.3.7 or earlier and sensitive admin functions are accessible without authentication or capability checks, the environment is affected by this missing authorization 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

Implement proper authorization checks on all sensitive endpoints and functions within the VW Wedding plugin, ensuring that access control security levels are correctly configured and enforced for all user roles.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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