CVE-2013-7189
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 · uneditedMultiple SQL injection vulnerabilities in iScripts AutoHoster, possibly 2.4, allow remote attackers to execute arbitrary SQL commands via the cmbdomain parameter to (1) checktransferstatus.php, (2) checktransferstatusbck.php, or (3) additionalsettings.php; or (4) invno parameter to payinvoiceothers.php.
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 confidenceMultiple SQL injection vulnerabilities in iScripts AutoHoster allow remote attackers to execute arbitrary SQL commands via the cmbdomain parameter in checktransferstatus.php, checktransferstatusbck.php, and additionalsettings.php, and via the invno parameter in payinvoiceothers.php.
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= 2.4CVSS 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.
-
Verify iScripts AutoHoster installationLocate the AutoHoster installation directory on the web server. Look for the main application folder containing PHP files like index.php, checktransferstatus.php, and payinvoiceothers.php.Affected if The application directory contains iScripts AutoHoster PHP files.
-
Confirm installed version is 2.4Check the version file, footer, or admin dashboard for the exact version number. Look for a version.php file or a version identifier in the application header/footer files.Affected if The installed version is exactly 2.4.
-
Verify affected PHP files existCheck for the presence of checktransferstatus.php, checktransferstatusbck.php, additionalsettings.php, and payinvoiceothers.php in the web-accessible directory.Affected if Any of these four PHP files are present in the installation.
-
Inspect cmbdomain parameter usageOpen checktransferstatus.php, checktransferstatusbck.php, and additionalsettings.php. Search for code that uses the cmbdomain parameter directly in SQL queries without sanitization or parameterized queries.Affected if The cmbdomain parameter is used in SQL queries without prepared statements or proper escaping.
-
Inspect invno parameter usageOpen payinvoiceothers.php and locate code that handles the invno parameter. Examine how it is incorporated into SQL queries.Affected if The invno parameter is used in SQL queries without prepared statements or proper escaping.
A user is affected if they have iScripts AutoHoster version 2.4 installed with the vulnerable PHP files present and the cmbdomain or invno parameters used unsafely in 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 dataImplement parameterized queries or prepared statements for all database interactions using the cmbdomain and invno parameters. Validate and sanitize all user input before using it in SQL queries.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-7189 — 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-2013-7189 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