# CVE-2025-60511: Missing authorization in n/a

> Authenticated students can impersonate other users' blocks to access sensitive data and modify model behavior due to insufficient parameter validation.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A: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:** 21 Oct 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-8wv9-5592-c67m

## What is CVE-2025-60511?

CVE-2025-60511 is a medium-severity missing authorization vulnerability in n/a, published on 21 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Moodle OpenAI Chat Block plugin 3.0.1 (2025021700) suffers from an Insecure Direct Object Reference (IDOR) vulnerability due to insufficient validation of the blockId parameter in /blocks/openai_chat/api/completion.php. An authenticated student can impersonate another user's block (e.g., administrator) and send queries that are executed with that block's configuration. This can expose administrator-only Source of Truth entries, alter model behavior, and potentially misuse API resources.

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

## Which versions are affected by CVE-2025-60511?


## How do I fix CVE-2025-60511?

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

## Is CVE-2025-60511 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-60511 and fix it if it is affected.

What it is: CVE-2025-60511 is a medium-severity missing authorization vulnerability in n/a, published on 21 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-60511 in the wild and no public exploit code.

Affected product: n/a. 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-2025-60511/ (Markdown: https://insights.sbomify.com/CVE-2025-60511/index.md)
```

## Sources

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

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