dbcve.org
OpensisApplication · Os4ed

CVE-2023-38880

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
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
The Community Edition version 9.0 of OS4ED's openSIS Classic has a broken access control vulnerability in the database backup functionality. Whenever an admin generates a database backup, the backup is stored in the web root while the file name has a format of "opensisBackup<date>.sql" (e.g. "opensisBackup07-20-2023.sql"), i.e. can easily be guessed. This file can be accessed by any unauthenticated actor and contains a dump of the whole database including password hashes.

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

In openSIS Classic CE 9.0, the admin database backup function stores SQL dumps in the web root using a predictable naming pattern (opensisBackupMM-DD-YYYY.sql). Due to missing access controls, any unauthenticated user can directly request and download these backup files, exposing the entire database contents including plaintext-equivalent password hashes.

MitigationRelocate backup storage outside the web-accessible directory, implement proper authentication checks on backup download endpoints, and use cryptographically random filenames instead of date-based patterns.

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

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

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. Identify openSIS installation and version
    Locate the openSIS installation directory and check for a version file or the software itself. Common paths include /var/www/html/opensis or similar web root locations. Look for version identifiers in the source code or admin interface.
    Affected if The installed version is exactly 9.0 (os4ed Opensis CE 9.0)
  2. Locate backup files in web root
    Search the web-accessible directory for SQL backup files matching the pattern openSISBackup*.sql. On Linux: find /var/www -name 'opensisBackup*.sql' 2>/dev/null. Check directories like /backup, /data, or the root of the web application.
    Affected if Any SQL backup files exist in the web root or subdirectories accessible via HTTP
  3. Test unauthenticated backup download access
    Use a web browser or curl to request a backup file directly via HTTP. For example: curl http://your-domain/opensisBackup12-31-2023.sql. Try common date patterns to guess backup filenames.
    Affected if The backup file downloads without requiring any authentication or login
  4. Verify backup directory is web-accessible
    Check the web server configuration (Apache/Nginx) to confirm the directory containing backups is not blocked from HTTP access. Ensure there is no .htaccess rule or web server config denying access to .sql files.
    Affected if The backup directory is served by the web server and accessible without restrictions

You are affected if you are running openSIS version 9.0 and SQL backup files are accessible via direct HTTP requests without authentication.

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

Relocate backup storage outside the web-accessible directory, implement proper authentication checks on backup download endpoints, and use cryptographically random filenames instead of date-based patterns.

Recommended fix Moderate confidence

A newer version of openSIS Classic Community Edition (version > 9.0) from OS4ED

  1. Check the official OS4ED openSIS downloads page (www.os4ed.com) or the openSIS GitHub repository for the latest version of openSIS Classic Community Edition
  2. Identify a version newer than 9.0 that includes the security fix for CVE-2023-38880
  3. Download the updated version from the official source
  4. Before upgrading, backup your current openSIS installation and database
  5. Install the new version following the standard upgrade documentation
  6. Verify that the database backup functionality now properly restricts access to backup files
  7. Confirm that backup files are either moved outside the web root or protected by authentication
Caveat Review release notes for any breaking changes between version 9.0 and the target upgrade version before proceeding

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
  • 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-2023-38880 — 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-38880 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