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

CVE-2026-2997

MEDIUM · 5.4 CVSS v3.1 Published 2026-02-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/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
Tronclass developed by WisdomGarden has a Insecure Direct Object Reference vulnerability. After obtaining a course ID, authenticated remote attackers to modify a specific parameter to obtain a course invitation code, thereby joining any course.

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

Tronclass by WisdomGarden contains an Insecure Direct Object Reference (IDOR) vulnerability that allows authenticated users to access course invitation codes for any course by manipulating a parameter tied to a course ID. The application fails to verify that the authenticated user has legitimate access to the specific course before returning its invitation code, enabling unauthorized course enrollment.

MitigationImplement proper authorization checks to validate user permissions before returning course invitation codes; ensure users can only access invitation codes for courses they are legitimately enrolled in or authorized to access.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 Tronclass installation
    Locate the Tronclass application in your environment - check for installed packages, running services, or web application directories. Look for 'tronclass' or 'WisdomGarden' in installed software inventories.
    Affected if Tronclass by WisdomGarden is present in the environment
  2. Determine Tronclass version
    Check the installed version of Tronclass against any release notes or version documentation. Common methods: review software bill of materials, check application headers, or query the application's about/version endpoint if available.
    Affected if Any version of Tronclass is installed (no specific version ranges provided)
  3. Locate the course invitation code feature
    Identify the API endpoint or web page that handles course invitation codes. Look for endpoints related to course enrollment, invitation codes, or course access. Common patterns include URLs with 'invitation', 'enroll', 'course', or 'join' in the path.
    Affected if The course invitation code functionality exists in the deployment
  4. Test IDOR vulnerability with course ID parameter
    Using an authenticated user account, attempt to access course invitation codes by manipulating the course ID parameter in the relevant endpoint. Test with course IDs outside the user's enrolled courses. Inspect HTTP requests/responses to see if the application returns invitation codes for unauthorized courses.
    Affected if The application returns invitation codes for courses the authenticated user is not enrolled in when the course ID parameter is modified
  5. Verify authorization logic for course access
    Review the application's backend code or proxy logs to determine if authorization checks occur before returning invitation codes. Check if the user-course membership is validated before exposing the invitation code.
    Affected if No authorization check is performed before returning course invitation codes, or the check can be bypassed

A user is affected if they have Tronclass deployed and the application returns course invitation codes for courses the authenticated user is not authorized to access when manipulating the course ID 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 authorization checks to validate user permissions before returning course invitation codes; ensure users can only access invitation codes for courses they are legitimately enrolled in or authorized to access.

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-2026-2997 — 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-2026-2997 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