# CVE-2026-64969: Insecure Direct Object Reference in ATutor

> Authenticated users can delete other users' profile pictures by manipulating member IDs, affecting ATutor LMS which is no longer supported.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Aug 2026
- **Updated:** 20 Aug 2026
- **Also known as:** GHSA-7g99-p5c5-4r5r

## What is CVE-2026-64969?

CVE-2026-64969 is a medium-severity missing authorization vulnerability in ATutor, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ATutor is vulnerable to Insecure Direct Object Reference (IDOR) attack in profile picture related endpoints. Any authenticated user, including a student, can supply another user's member_id in a POST request to the profile album endpoint and permanently delete that user's profile picture, including those of instructors and administrators.

Product is no longer actively supported and the vulnerabilities have not been fixed. Only version 2.2.4 was tested and confirmed as vulnerable, other versions were not tested but might also be vulnerable.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-64969?


## How do I fix CVE-2026-64969?

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

## Is CVE-2026-64969 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-64969 and fix it if it is affected.

What it is: CVE-2026-64969 is a medium-severity missing authorization vulnerability in ATutor, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-64969 in the wild and no public exploit code.

Affected product: ATutor. 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-2026-64969/ (Markdown: https://insights.sbomify.com/CVE-2026-64969/index.md)
```

## Sources

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

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