Missing AuthorizationWeakness · CWE-862

CVE-2026-32435

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-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

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 Pet Shop vw-pet-shop allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects VW Pet Shop: from n/a through <= 1.4.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

Missing authorization vulnerability in VW Pet Shop allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to functionality or data that should be restricted based on user privileges.

MitigationImplement proper authorization checks at all access control points and ensure security levels are correctly enforced throughout the application, verifying that each user role can only access permitted resources.

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 Pet Shop application version
    Locate the application installation directory and check for version information in configuration files, README files, or the application's main entry point. Common locations include version.xml, app.config, or a footer/version display in the web interface.
    Affected if The installed version cannot be determined or is an older release that may contain the authorization flaw.
  2. Review access control security level configuration
    Inspect configuration files (such as web.config, security.xml, or application.properties) for security level settings related to access control. Look for parameters controlling authorization enforcement, role-based access, or permission levels.
    Affected if Security levels are set to low, disabled, or misconfigured, allowing privilege escalation.
  3. Verify role-based access control (RBAC) settings
    Examine user role definitions and permission mappings in the database or configuration. Check which roles exist (admin, user, guest) and verify the assigned permissions for each role.
    Affected if Roles lack proper permission boundaries or users can access functions outside their assigned role's privileges.
  4. Test authorization enforcement on sensitive endpoints
    Attempt to access privileged functions or data endpoints using a lower-privilege account. Check if admin-only features, user data, or administrative panels are accessible without proper authentication level.
    Affected if Lower-privileged users can access restricted functionality that should require higher privileges.
  5. Inspect authentication and authorization code paths
    Review source code or application logic for authorization checks before executing sensitive operations. Verify that each protected function contains explicit authorization validation.
    Affected if Protected functions lack authorization checks or rely solely on authentication (logged-in status) without verifying role permissions.

The environment is affected if VW Pet Shop is installed and the access control configuration permits unauthorized access to restricted functionality or data based on user privileges.

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 at all access control points and ensure security levels are correctly enforced throughout the application, verifying that each user role can only access permitted resources.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32435 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-32435 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