Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2024-50485

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Incorrect Privilege Assignment vulnerability in Udit Rawat Exam Matrix exam-matrix allows Privilege Escalation.This issue affects Exam Matrix: from n/a through <= 1.5.

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

A critical privilege escalation vulnerability exists in Exam Matrix versions up to 1.5 where the application improperly assigns user privileges, allowing authenticated or potentially unauthenticated users to gain administrative or elevated access beyond what they should be authorized for.

MitigationUpgrade Exam Matrix to the latest version beyond 1.5 and conduct a comprehensive authorization code review to identify and remediate all insecure privilege assignment pathways.

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

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

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

  1. Identify installed Exam Matrix version
    Locate the version identifier in the application (check version file, about page, footer, or config files within the Exam Matrix installation directory). Compare this version number against the affected range (version 1.5 and below are vulnerable).
    Affected if The installed version is 1.5 or any version lower than 1.5
  2. Review user role configuration
    Access the application admin panel or examine the database/role configuration files to list all defined user roles and their assigned privilege levels. Identify if any roles have administrative or elevated permissions beyond what is documented or intended.
    Affected if Any user role has administrative privileges that should not be assigned based on the principle of least privilege
  3. Inspect privilege assignment endpoints
    Examine the application source code or API endpoints that handle user privilege modifications (such as role assignment, permission updates, or user promotion functions). Check if these endpoints can be accessed without proper authorization checks.
    Affected if Endpoints exist that allow privilege escalation without requiring admin-level authentication or proper authorization validation
  4. Verify admin account inventory
    List all user accounts with administrative or elevated access within the application. Cross-reference against records of accounts created through legitimate administrative processes.
    Affected if There are administrative accounts present that were not created through the proper provisioning workflow or that belong to users who should not have elevated access

A user is affected if their Exam Matrix installation is version 1.5 or lower, or if unauthorized privilege escalation pathways or unexpected admin accounts exist in the system.

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

Upgrade Exam Matrix to the latest version beyond 1.5 and conduct a comprehensive authorization code review to identify and remediate all insecure privilege assignment pathways.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-50485 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