# CVE-2024-6738: WisdomGarden Tronclass - Broken Access Control

> Unauthenticated attackers can access specific files via the thumbnail API due to missing access controls in WisdomGarden Tronclass.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jul 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-6phm-74mw-7r5r

## What is CVE-2024-6738?

CVE-2024-6738 is a medium-severity missing authorization vulnerability in WisdomGarden Tronclass, published on 15 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The tumbnail API of Tronclass from WisdomGarden lacks proper access control, allowing unauthenticated remote attackers to obtain certain specific files by modifying the URL.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2024-6738?

It affects 1 product.


Products: Wisdomgarden Tronclass.

## How do I fix CVE-2024-6738?

No fix has been published for CVE-2024-6738 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-6738 being exploited?

There is no known exploitation of CVE-2024-6738 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6738 and fix it if it is affected.

What it is: CVE-2024-6738 is a medium-severity missing authorization vulnerability in WisdomGarden Tronclass, published on 15 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-6738 in the wild and no public exploit code.

Affected product: WisdomGarden Tronclass. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-6738/ (Markdown: https://insights.sbomify.com/CVE-2024-6738/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-6738
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-6738
- OSV: https://osv.dev/vulnerability/CVE-2024-6738

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-6738/
Summaries are generated and may contain mistakes; the official description above is the record.