dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2025-10763

MEDIUM · 6.3 CVSS v3.1 Published 2025-09-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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
A vulnerability was determined in academico-sis academico up to d9a9e2636fbf7e5845ee086bcb03ca62faceb6ab. Affected by this issue is some unknown functionality of the file /edit-photo of the component Profile Picture Handler. This manipulation causes unrestricted upload. The attack is possible to be carried out remotely. The exploit has been publicly disclosed and may be utilized. This product adopts a rolling release strategy to maintain continuous delivery The vendor was contacted early about this disclosure but did not respond in any way.

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

The academico-sis application has an unrestricted file upload vulnerability in the profile picture handler at /edit-photo. The component fails to properly validate uploaded file types, sizes, or content, allowing remote attackers to upload arbitrary files including potentially malicious web shells or executables to the server.

MitigationImplement strict allowlist-based file validation including magic byte checking, enforce maximum file size limits, store uploads outside the web root with randomized filenames, and add proper content-type and extension verification before accepting any file.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 the /edit-photo endpoint is accessible
    Visit the application's profile editing area or directly access /edit-photo in a web browser to verify the endpoint exists and responds.
    Affected if The endpoint returns a form or accepts requests, indicating the upload feature is present.
  2. Test for unrestricted file type acceptance
    Send a test HTTP POST request to /edit-photo with a non-image file (e.g., a .txt file containing arbitrary text or a .php file) using curl or a web proxy. Observe whether the server accepts and stores the file.
    Affected if The server accepts and returns success for a file that is not a valid image type, indicating no file type validation is enforced.
  3. Verify uploaded files are web-accessible
    After a test upload, attempt to access the uploaded file directly via the web (e.g., guess the URL path or check the response for a download/link).
    Affected if Uploaded files are directly accessible via a URL within the web root, allowing execution of uploaded scripts.
  4. Check for missing content-type validation
    Intercept the upload request and modify the Content-Type header to a non-image value (e.g., application/octet-stream) while sending an image file extension. Submit and observe if accepted.
    Affected if The server accepts files regardless of the Content-Type header, indicating weak or no server-side validation.
  5. Inspect for absence of magic byte validation
    Create a file with a valid image extension (e.g., .jpg) but containing non-image content (like text or PHP code). Upload it and check if it is accepted.
    Affected if The server accepts files based solely on extension without validating actual file content (magic bytes).

A user is affected if the /edit-photo endpoint exists and accepts files without proper server-side validation of type, content, or size, or if uploaded files are stored in a web-accessible location.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict allowlist-based file validation including magic byte checking, enforce maximum file size limits, store uploads outside the web root with randomized filenames, and add proper content-type and extension verification before accepting any file.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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