CVE-2025-52804
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 · uneditedMissing Authorization vulnerability in uxper Nuss nuss allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Nuss: from n/a through <= 1.3.7.1.
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 confidenceMissing authorization vulnerability in Nuss allows unauthenticated or unauthorized users to access functionality that should be constrained by Access Control Lists (ACLs). The vulnerability exists in versions up to and including 1.3.7.1, enabling attackers to bypass ACL restrictions and invoke protected functions or features without proper permission checks.
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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Nuss versionQuery the Nuss application for its version using standard methods such as: checking the application's --version flag, inspecting a VERSION or version.py file in the installation directory, querying the package manager if installed as a package, or accessing a version API endpoint if available.Affected if The installed version is 1.3.7.1 or any earlier version (any version up to and including 1.3.7.1)
-
Identify ACL-protected functions or featuresReview application documentation, source code, or configuration to enumerate functions, API endpoints, or features that should be restricted by Access Control Lists. Look for decorators, middleware, or permission checks that define protected operations.Affected if The application contains ACL-protected functionality that should require authorization
-
Test unauthorized access to protected endpointsSend HTTP requests or invoke protected functions without providing authentication credentials or authorization tokens. Compare responses when authenticated versus unauthenticated. Check if protected operations complete successfully without proper authorization headers or session tokens.Affected if Protected functions execute or return successful responses when accessed without valid authentication or authorization
-
Verify authorization check implementationInspect the source code of protected functions to confirm that authorization logic (such as permission validation, role checks, or ACL enforcement) exists and executes before sensitive operations. Look for missing or bypassed authorization decorators or middleware.Affected if Protected functions lack proper authorization validation or allow execution without permission checks
If the Nuss version is 1.3.7.1 or lower AND ACL-protected functions can be accessed or executed without proper authorization, the environment is vulnerable to CVE-2025-52804.
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 proper authorization checks on all sensitive functions and ensure ACL constraints are correctly enforced for every protected operation. Upgrade to a version beyond 1.3.7.1 if a patched release is available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52804 — 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-2025-52804 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