dbcve.org
OpensisApplication · Os4ed

CVE-2023-38884

HIGH · 7.5 CVSS v3.1 Published 2023-11-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 Insecure Direct Object Reference (IDOR) vulnerability in the Community Edition version 9.0 of openSIS Classic allows an unauthenticated remote attacker to access any student's files by visiting '/assets/studentfiles/<studentId>-<filename>'

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

An IDOR vulnerability in openSIS Classic 9.0 allows unauthenticated remote attackers to access arbitrary student files by manipulating student IDs in the '/assets/studentfiles/<studentId>-<filename>' path, bypassing authentication controls.

MitigationImplement proper authentication and authorization checks to verify the requesting user has legitimate access to the specific student file before serving it; consider implementing indirect object references and session-based access controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpensisApplication
Affected:= 9.0

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 openSIS Classic version
    Check the installed version of openSIS Classic. This may be visible in the application header, footer, about page, or in a version configuration file within the installation directory.
    Affected if The installed version is openSIS Classic 9.0
  2. Identify if studentfiles endpoint is exposed
    Attempt to access the path /assets/studentfiles/ on the web server. This may return a directory listing or indicate the path exists.
    Affected if The /assets/studentfiles/ directory is accessible via the web server
  3. Test unauthenticated file access
    Send an HTTP GET request to /assets/studentfiles/1-test.jpg (or any plausible studentId-filename combination) without providing any authentication credentials. Check if the server returns a file instead of redirecting to a login page.
    Affected if Student files are served without requiring authentication
  4. Verify IDOR with different student IDs
    Attempt to access the same endpoint with different numeric student IDs (e.g., /assets/studentfiles/1-filename, /assets/studentfiles/2-filename, /assets/studentfiles/100-filename) without being logged in. Compare whether different student files can be retrieved.
    Affected if Different student IDs return different student files without authentication, indicating the IDOR vulnerability exists

If openSIS Classic 9.0 is running and the /assets/studentfiles/ endpoint serves files to unauthenticated users by simply varying the student ID, the environment is affected by this CVE.

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 proper authentication and authorization checks to verify the requesting user has legitimate access to the specific student file before serving it; consider implementing indirect object references and session-based access controls.

Recommended fix Moderate confidence

Latest stable release of openSIS Classic (Community Edition) - version > 9.0

  1. 1. Navigate to the official openSIS download page at www.os4ed.com to obtain the latest stable release
  2. 2. Download the most recent version of openSIS Classic (Community Edition)
  3. 3. Backup the current installation including the database and all student files
  4. 4. Install the new version on a test environment first to verify compatibility
  5. 5. Deploy the upgraded version to production after confirming functionality
Caveat Minor version upgrades may include database schema changes; test thoroughly before production deployment

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

Fix this in Opensis Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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