dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2024-45877

MEDIUM · 6.5 CVSS v3.1 Published 2024-11-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
baltic-it TOPqw Webportal v1.35.283.2 is vulnerable to Incorrect Access Control in the User Management function in /Apps/TOPqw/BenutzerManagement.aspx. This allows a low privileged user to access all modules in the web portal, view and manipulate information and permissions of other users, lock other user or unlock the own account, change the password of other users, create new users or delete existing users and view, manipulate and delete reference data.

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 confidence

The TOPqw Webportal fails to enforce proper authorization checks on the User Management page (/Apps/TOPqw/BenutzerManagement.aspx), allowing authenticated low-privilege users to bypass role-based access controls and perform administrative functions. This Broken Access Control vulnerability enables vertical privilege escalation where standard users can manage other user accounts, modify permissions, change passwords, and access all portal modules.

MitigationImplement and enforce role-based access control (RBAC) on all administrative functions, ensuring the application validates user privileges server-side before allowing user management operations, password changes, or access to sensitive modules.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify TOPqw Webportal installation
    Check for the presence of the TOPqw Webportal application in the web server's directory structure, typically found under /Apps/TOPqw/ or as configured in the web server. Look for the BenutzerManagement.aspx page at the expected path.
    Affected if The application is installed and the User Management page exists at /Apps/TOPqw/BenutzerManagement.aspx
  2. Verify User Management page accessibility
    Attempt to access the User Management page directly via HTTP/HTTPS request to /Apps/TOPqw/BenutzerManagement.aspx using a low-privilege authenticated user account (standard user with no administrative roles).
    Affected if The page loads or responds without returning an authorization error (403 Forbidden or access denied message)
  3. Check for privilege escalation capability
    With a low-privilege user session, attempt to perform administrative actions on the User Management page: create a new user, modify an existing user's role or permissions, change another user's password, or access portal modules outside the user's assigned scope.
    Affected if The application allows any of these administrative operations to succeed without returning an authorization failure response
  4. Inspect server-side authorization controls
    Review the application's source code, configuration files, or web.config to verify whether role-based access control (RBAC) is enforced on the User Management page server-side before processing any user management requests.
    Affected if No server-side role validation is found, or the page allows all authenticated users to execute management functions regardless of their assigned role

A user is affected if the TOPqw Webportal is running and the User Management page at /Apps/TOPqw/BenutzerManagement.aspx is accessible to low-privilege authenticated users who can perform administrative actions without proper authorization checks.

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 and enforce role-based access control (RBAC) on all administrative functions, ensuring the application validates user privileges server-side before allowing user management operations, password changes, or access to sensitive modules.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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