dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-10024

HIGH · 7.5 CVSS v3.1 Published 2026-01-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Authorization Bypass Through User-Controlled Key vulnerability in EXERT Computer Technologies Software Ltd. Co. Education Management System allows Parameter Injection. This issue affects Education Management System: through 23.09.2025.

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

This is an authorization bypass vulnerability in the Education Management System where an attacker can manipulate a user-controlled parameter (such as a record ID or reference) to access resources or functionality they are not authorized to access. The parameter injection allows bypassing authentication or authorization checks by modifying the parameter value to reference other users' data or admin functions.

MitigationImplement proper server-side authorization checks that validate the authenticated user's permissions before allowing access to any resource identified by user-supplied parameters. Use indirect object references and enforce least-privilege access controls.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 user-controlled parameter usage
    Review application code or proxy logs to identify endpoints that accept user-supplied parameters (such as IDs, record references, or file paths) used to access data or functionality. Look for GET/POST parameters like id=, record_id=, user_id=, ref=, or similar patterns.
    Affected if The application uses URL parameters to reference records or resources without proper validation.
  2. Locate authorization logic for parameter-based access
    Search the codebase for authorization or permission check functions that validate whether the authenticated user is permitted to access a specific resource identified by a user-supplied parameter. Look for patterns like 'checkPermission', 'verifyAccess', 'authorize', 'isOwner', or 'canAccess'.
    Affected if No server-side authorization check exists that validates the user's permissions before processing the parameter value.
  3. Test for insecure direct object reference
    Log in as a low-privilege user (such as a student or standard user) and attempt to manipulate numeric or reference parameters to access records belonging to other users or administrative functions. For example, if viewing own record at /student/record?id=123, try id=124 or id=1 to see if unauthorized data is returned.
    Affected if Modifying the parameter value grants access to records or functions belonging to other users or elevated roles.
  4. Verify role-based access control enforcement
    Examine whether the application enforces role-based access control (RBAC) at the function or API level. Confirm that admin-only functions cannot be triggered by manipulating parameters when authenticated as a non-admin user.
    Affected if User-supplied parameters can be manipulated to invoke administrative functions or access admin-only areas without proper role verification.
  5. Check for indirect object reference implementation
    Review whether the system uses indirect (mapped) object references instead of direct database IDs in URLs and API calls. Verify that exposed internal IDs are mapped to random or opaque values that cannot be easily guessed.
    Affected if Direct database record IDs or sequential identifiers are exposed in URLs or API parameters without abstraction or access controls.

Your environment is affected if the Education Management System uses user-supplied parameters to access resources and lacks proper server-side authorization validation that confirms the authenticated user has permission to access the specific resource referenced by that parameter.

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 proper server-side authorization checks that validate the authenticated user's permissions before allowing access to any resource identified by user-supplied parameters. Use indirect object references and enforce least-privilege access controls.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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