dbcve.org
Sqlite ManagerDatabase / datastore

CVE-2008-0516

HIGH · 9.3 CVSS v2.0 Published 2008-01-31
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
PHP remote file inclusion vulnerability in spaw/dialogs/confirm.php in SQLiteManager 1.2.0 allows remote attackers to execute arbitrary PHP code via a URL in the spaw_root parameter. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

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

SQLiteManager 1.2.0 contains a remote file inclusion vulnerability in spaw/dialogs/confirm.php where the spaw_root parameter is not validated, allowing attackers to inject a malicious URL and execute arbitrary PHP code on the server.

MitigationUpgrade to a patched version of SQLiteManager or implement strict input validation on the spaw_root parameter to ensure only trusted local paths are accepted; if the spaw component is unused, consider removing it entirely.

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
Sqlite ManagerDatabase / datastore
Affected:= 1.2

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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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. Locate SQLiteManager installation
    Search the web server document root for sqlitemanager directories, or check common paths such as /sqlite-manager/, /sqlitemanager/, or /db/sqlite. Look for a file named 'Version' or check the main PHP files for version strings matching 1.2.x
    Affected if SQLiteManager version 1.2.0 or 1.2.x is found on the server
  2. Identify the vulnerable spaw component
    Check if the spaw directory exists within the SQLiteManager installation path. Specifically look for spaw/dialogs/confirm.php
    Affected if The file spaw/dialogs/confirm.php exists in the SQLiteManager installation
  3. Verify spaw_root parameter handling
    Examine the confirm.php file for the spaw_root parameter usage. Look for whether the parameter is validated or sanitized before being used in include/require statements
    Affected if The spaw_root parameter is used in include/require without validation, or the code does not restrict it to local paths only
  4. Test for remote file inclusion possibility
    If the application is accessible, attempt a controlled test request to spaw/dialogs/confirm.php with a spaw_root parameter pointing to a harmless local file or observe if the parameter is reflected in server responses
    Affected if The spaw_root parameter accepts external URLs or allows path traversal, enabling remote file inclusion

The server is affected if SQLiteManager 1.2.x is installed with the spaw component present and the spaw_root parameter in spaw/dialogs/confirm.php lacks proper validation, allowing arbitrary code execution via remote file inclusion.

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

Upgrade to a patched version of SQLiteManager or implement strict input validation on the spaw_root parameter to ensure only trusted local paths are accepted; if the spaw component is unused, consider removing it entirely.

Recommended fix Moderate confidence

SQLiteManager 1.2.4 or latest stable release

  1. 1. Identify all deployments of SQLiteManager version 1.2.0 in your environment
  2. 2. Download the latest stable version of SQLiteManager from the official project repository (sourceforge.net/projects/sqlitemanager)
  3. 3. Backup all existing SQLiteManager configuration files and databases
  4. 4. Replace the existing SQLiteManager installation with the new version
  5. 5. Restore your configuration files to the new installation
  6. 6. Verify the spaw directory and confirm.php file have been updated or removed as part of the upgrade
  7. 7. Test that database management functionality works correctly
  8. 8. Verify the vulnerability is no longer present by confirming spaw_root parameter is no longer used or is properly sanitized
Caveat Minor: Review any configuration changes between 1.2.0 and newer versions; ensure custom theming or modifications are compatible

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

Fix this in Sqlite Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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