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

> Unauthenticated attackers can retrieve user profile pictures by guessing identifiers due to missing authorization checks in PRONOTE.

- **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:** 16 Mar 2026
- **Updated:** 16 Mar 2026
- **Also known as:** GHSA-8rhg-93pw-jwq6

## What is CVE-2025-69727?

CVE-2025-69727 is a medium-severity missing authorization vulnerability in n/a, published on 16 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An Incorrect Access Control vulnerability exists in INDEX-EDUCATION PRONOTE prior to 2025.2.8. The affected components (index.js and composeUrlImgPhotoIndividu) allow the construction of direct URLs to user profile images based solely on predictable identifiers such as user IDs and names. Due to missing authorization checks and lack of rate-limiting when generating or accessing these URLs, an unauthenticated or unauthorized actor may retrieve profile pictures of users by crafting requests with guessed or known identifiers.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2025-69727 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-69727 exists.

Public exploit code:

- CVE-2025-69727 (github_poc): https://github.com/0xZeroSec/CVE-2025-69727

## Fix prompt for AI coding agents

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

What it is: CVE-2025-69727 is a medium-severity missing authorization vulnerability in n/a, published on 16 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-69727 exists.

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-69727/ (Markdown: https://insights.sbomify.com/CVE-2025-69727/index.md)
```

## Sources

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

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