Authorization bypass via missing user-status checks
Published Apr 20, 2026 · Updated Apr 20, 2026
Incorrect authorization in Nginx UI before 2.3.4 allows remote authenticated users to retain API access after account disablement. GetTokenUser and GetTokenUserByShortToken validate token integrity and expiration but return cached or database user objects without checking user.Status. Exploitation requires a previously issued, unexpired token and permits sensitive configuration reads, authenticated state changes, and creation of a replacement account.
Summary
What happened
Incorrect authorization in Nginx UI before 2.3.4 allows remote authenticated users to retain API access after account disablement. GetTokenUser and GetTokenUserByShortToken validate token integrity and expiration but return cached or database user objects without checking user.Status. Exploitation requires a previously issued, unexpired token and permits sensitive configuration reads, authenticated state changes, and creation of a replacement account.
The record
- CVE
- CVE-2026-33031
- Published
- Apr 20, 2026
- Updated
- Apr 20, 2026
- Vendor
- 0xJacky
- Product
- Nginx UI
- Classifications
- CWE-284, CWE-863, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 20, 2026CVE publishedPublication date reported by the CVE source.
- Apr 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.3.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Vendor-advisory proof-of-concept videoproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo