dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-5666

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-06
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
A vulnerability was detected in code-projects Online FIR System 1.0. Affected by this issue is some unknown functionality of the file /complaints.sql of the component SQL Database Backup File Handler. The manipulation results in insecure storage of sensitive information. The attack may be performed from remote. The exploit is now public and may be used.

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 vulnerability exists in the SQL Database Backup File Handler component of Online FIR System 1.0, specifically in the handling of the /complaints.sql file. The manipulation of this file results in insecure storage of sensitive information, likely due to improper access controls on the backup file that allows unauthorized exposure of potentially sensitive complaint data.

MitigationRestrict access to SQL backup files by moving them outside the web-accessible directory, implement proper file permissions, and ensure backup files are not stored in publicly accessible locations. Review and secure all database backup file handlers in the application.

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 Online FIR System 1.0 is installed
    Identify if the Online FIR System application is present in your environment by checking web server document roots or application directories for the typical FIR system file structure.
    Affected if The application is found to be deployed and running in the environment.
  2. Locate the complaints.sql backup file
    Search the web application directory tree for a file named complaints.sql, typically found in the root or backup directories accessible via HTTP requests.
    Affected if The file complaints.sql exists within the web-accessible application directory.
  3. Verify web accessibility of the SQL backup file
    Attempt to access http://[host]/complaints.sql (or the equivalent path) via a web browser or curl command to determine if the file is publicly retrievable.
    Affected if The server returns the SQL file contents via HTTP, indicating the file is publicly accessible without authentication.
  4. Check file permissions on the backup file
    If file system access is available, inspect file permissions using 'ls -la' or equivalent to verify if world-readable permissions are set on the complaints.sql file.
    Affected if The file permissions allow read access by unauthenticated users or the web server user.
  5. Inspect the backup file contents for sensitive data
    If accessible, examine the complaints.sql file for sensitive information such as user credentials, personal identifiable information (PII), or complaint records that should not be publicly exposed.
    Affected if The backup file contains unencrypted sensitive data that would not be intended for public disclosure.

If the Online FIR System 1.0 is running and the complaints.sql file is accessible via HTTP without authentication, the environment is affected by this vulnerability.

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

Restrict access to SQL backup files by moving them outside the web-accessible directory, implement proper file permissions, and ensure backup files are not stored in publicly accessible locations. Review and secure all database backup file handlers in the application.

Recommended fix Low confidence
  1. Identify the web root directory where the Online FIR System 1.0 is deployed
  2. Locate and delete the /complaints.sql file from the web-accessible directory (or any publicly accessible folder)
  3. If the SQL backup is needed for restoration purposes, move it to a secure, non-web-accessible location outside the public document root
  4. Configure the web server (Apache/Nginx) to deny access to .sql files by adding a rule (e.g., in .htaccess: 'RewriteRule \.sql$ - [F,L]' or in nginx: 'location ~ \.sql { deny all; }')
  5. Verify the file is no longer accessible by attempting to download it via HTTP/HTTPS
  6. Audit the deployment for any other exposed backup files (.sql, .bak, .zip) in web-accessible directories

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

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-2026-5666 — 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-2026-5666 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