CVE-2026-33030
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 · uneditedNginx UI is a web user interface for the Nginx web server. In versions 2.3.3 and prior, Nginx-UI contains an Insecure Direct Object Reference (IDOR) vulnerability that allows any authenticated user to access, modify, and delete resources belonging to other users. The application's base Model struct lacks a user_id field, and all resource endpoints perform queries by ID without verifying user ownership, enabling complete authorization bypass in multi-user environments. At time of publication, there are no publicly available patches.
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 · high confidenceNginx UI versions 2.3.3 and prior contain an IDOR vulnerability where the base Model struct lacks a user_id field, causing all resource endpoints to query by ID without ownership verification. This allows any authenticated user to access, modify, or delete resources belonging to other users in multi-user environments.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2.3.3CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Nginx UI installation and versionIdentify the installed Nginx UI version (e.g., via package manager, Docker image tag, or application interface) and compare it against the affected range: <= 2.3.3Affected if The installed version is 2.3.3 or lower
-
Determine if multi-user mode is enabledCheck the Nginx UI configuration for multi-user settings or the presence of user account functionality (consult product documentation for specific configuration file location and parameter names)Affected if Multi-user access or multiple user accounts are configured and active
-
Verify resource access isolationLog in as one user and attempt to access, modify, or delete a resource known to belong to a different user (e.g., by manipulating API endpoint IDs or UI parameters)Affected if An authenticated user can access or manipulate another user's resources without authorization errors
-
Inspect the base Model struct for user_id fieldExamine the Nginx UI source code or binary for the base Model struct definition to determine whether a user_id field exists and is used for ownership verification on resource endpointsAffected if The base Model struct lacks a user_id field or authorization checks are not enforced on resource endpoints
A user is affected if Nginx UI version 2.3.3 or lower is running with multi-user mode enabled, and the base Model lacks user_id field for ownership verification, allowing unauthorized cross-user resource access.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement user ownership verification on all resource endpoints by adding user_id to the base Model and enforcing authorization checks; consider restricting multi-user access until a patch is available.
- Consultation8.0 h
- Implementation32.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $17,920.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33030 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-33030 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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