dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-5230

HIGH · 7.1 CVSS v3.1 Published 2026-06-15
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

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
Improper Access Control, Missing Authorization vulnerability in MIA Technology Inc. Pizzy Library allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects Pizzy Library: from 1.0.0.26250 before 1.3.9.26250.

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

The Pizzy Library from MIA Technology Inc. contains an improper access control vulnerability where missing authorization checks allow attackers to exploit incorrectly configured access control security levels. This enables unauthorized access to protected functionality or resources within applications using the library.

MitigationUpdate Pizzy Library to version 1.3.9.26250 or later to obtain the patched version with proper authorization controls. Review access control configurations in applications using the library to ensure security levels are correctly set.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Locate Pizzy Library in your environment
    Search your application dependencies, build artifacts, or installed packages for files or modules named 'pizzy' or 'Pizzy', and note the directory path where it is found.
    Affected if Pizzy Library is present in your application dependencies or runtime environment.
  2. Determine the installed Pizzy Library version
    Check the library's version metadata by inspecting the package.json, .dll, .jar, or version file located in the Pizzy Library path, or run a package manager query such as 'pip show pizzy', 'npm list pizzy', or 'dotnet list package' if applicable.
    Affected if The installed version is lower than 1.3.9.26250.
  3. Identify access control configuration for Pizzy
    Locate configuration files, XML files, JSON settings, or environment variables that define security levels, authorization rules, or access control policies for the Pizzy Library. Common locations include config/ directory, appsettings.json, web.config, or custom config files referenced in initialization code.
    Affected if Access control security levels are set to a weak, default, or permissive configuration that lacks explicit authorization enforcement.
  4. Verify if authorization checks are enforced on protected endpoints or functions
    Review application code or API routes that call Pizzy Library functionality to confirm whether authorization logic (such as role checks, permission validation, or authentication enforcement) is explicitly implemented before invoking protected methods.
    Affected if Protected functionality can be accessed without proper authorization validation or with security level set to allow unrestricted access.

You are affected if Pizzy Library version 1.3.9.26250 or higher is not in use, AND the access control security levels are configured with weak or missing authorization checks that permit unauthorized access to protected functionality.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Pizzy Library to version 1.3.9.26250 or later to obtain the patched version with proper authorization controls. Review access control configurations in applications using the library to ensure security levels are correctly set.

Recommended fix Moderate confidence

1.3.9.26250 or later

  1. 1. Identify all deployments of Pizzy Library in your environment
  2. 2. Check the current version of Pizzy Library (look for version 1.0.0.26250 through versions before 1.3.9.26250)
  3. 3. Obtain the fixed version 1.3.9.26250 or later from the vendor (MIA Technology Inc.)
  4. 4. Test the upgrade in a non-production environment first
  5. 5. Deploy the upgraded Pizzy Library version 1.3.9.26250 or later to production

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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