CVE-2015-7382
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 · uneditedSQL injection vulnerability in install.php in Web Reference Database (aka refbase) through 0.9.6 allows remote attackers to execute arbitrary SQL commands via the defaultCharacterSet parameter, a different issue than CVE-2015-6009.
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 confidenceA SQL injection vulnerability exists in the install.php script of the Web Reference Database (refbase) versions 0.9.6 and prior. The vulnerability stems from insufficient sanitization of the defaultCharacterSet parameter, allowing remote attackers to inject arbitrary SQL commands into database queries.
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<= 0.9.6CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Locate the install.php scriptSearch the web server document root for the file 'install.php' - common paths include /var/www/html/refbase/install.php or similar web directory pathsAffected if The install.php file exists in the web-accessible directory and has not been removed after initial setup
-
Identify the refbase versionCheck for a version file (VERSION, version.php, or similar) in the refbase installation directory, or view the header/comment section of core PHP files for a version stringAffected if The installed refbase version is 0.9.6 or any version prior to 0.9.6
-
Verify if install.php is accessibleAttempt to access the install.php URL via HTTP/HTTPS request (e.g., curl or browser request to http://[host]/refbase/install.php)Affected if The script returns a 200 OK response indicating it is accessible via the web
-
Confirm defaultCharacterSet parameter handlingInspect the install.php source code and locate the code handling the 'defaultCharacterSet' parameter - look for SQL query construction that uses this parameter without proper escaping or parameterized queriesAffected if The code shows direct insertion of the defaultCharacterSet parameter into SQL queries without sanitization or prepared statements
You are affected if refbase version 0.9.6 or prior is installed AND the install.php file remains in the web-accessible directory with the defaultCharacterSet parameter being passed unsanitized to SQL queries.
Generated from the published advisory. Verify against your own configuration.
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 dataThe install.php file should be removed after initial setup is complete, or input validation and parameterized queries should be implemented for the defaultCharacterSet parameter to prevent SQL injection.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7382 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-7382 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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