dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2025-69727

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
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.

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 · high confidence

PRONOTE web application exposes user profile images through predictable URLs constructed from user IDs and names without proper authorization validation. The index.js and composeUrlImgPhotoIndividu components generate direct image URLs that can be accessed by any unauthenticated attacker who can guess or obtain valid user identifiers.

MitigationImplement authorization checks to verify the requesting user has permission to access profile images before serving the resource, and add rate-limiting to prevent enumeration of valid user identifiers.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Confirm PRONOTE web application is present
    Identify if the target system runs the PRONOTE application by checking for pronote-related processes, services, or web application fingerprints (e.g., HTTP response headers, favicon, or default pronote paths)
    Affected if PRONOTE is installed and accessible on the network
  2. Locate the vulnerable index.js file
    Search the web application source code or deployment directory for index.js files containing the image URL generation logic, particularly looking for references to composeUrlImgPhotoIndividu or user profile image handling
    Affected if The index.js file contains code that constructs image URLs from user IDs without authorization checks
  3. Identify composeUrlImgPhotoIndividu function usage
    Examine the application code for the composeUrlImgPhotoIndividu component - search for this function name and verify it builds direct image URLs using user identifiers without validating session permissions
    Affected if The composeUrlImgPhotoIndividu function generates direct image URLs without performing authorization validation
  4. Test unauthorized profile image access
    Attempt to access profile image URLs constructed from valid user IDs (e.g., /api/image?userid=123 or similar patterns) without providing authentication credentials or valid session cookies
    Affected if Profile images are returned without requiring valid authentication or authorization tokens
  5. Verify authorization controls on image endpoints
    Inspect network requests when accessing profile images through the UI with a valid session, then compare to requests made without authentication to determine if the server validates access permissions before serving the image
    Affected if The server returns profile images to unauthenticated requests, indicating missing authorization checks

A user is affected if the PRONOTE application serves profile images to unauthenticated requests based solely on predictable user identifiers, without verifying the requester has permission to view those images.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement authorization checks to verify the requesting user has permission to access profile images before serving the resource, and add rate-limiting to prevent enumeration of valid user identifiers.

Recommended fix Moderate confidence

2025.2.8

  1. 1. Identify the current PRONOTE version currently installed on the server
  2. 2. Download the PRONOTE version 2025.2.8 or later from the official INDEX-EDUCATION distribution channels
  3. 3. Back up the current PRONOTE installation and database before proceeding with the upgrade
  4. 4. Apply the upgrade following INDEX-EDUCATION's standard upgrade procedures
  5. 5. Verify that the upgrade completed successfully and the application is operational
  6. 6. Test that profile image URLs now require proper authentication and authorization

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-69727 — 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-2025-69727 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