CVE-2013-7190
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 directory traversal vulnerabilities in iScripts AutoHoster, possibly 2.4, allow remote attackers to read arbitrary files via the (1) tmpid parameter to websitebuilder/showtemplateimage.php, (2) fname parameter to admin/downloadfile.php, or (3) id parameter to support/admin/csvdownload.php; or (4) have an unspecified impact via unspecified vectors in support/parser/main_smtp.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 directory traversal vulnerabilities in iScripts AutoHoster allow remote attackers to read arbitrary files by manipulating path traversal sequences (e.g., ../../) in the tmpid, fname, and id parameters across three PHP files, plus an unspecified impact in main_smtp.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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm iScripts AutoHoster is installedLocate the installation directory - typically found in web server document roots. Look for the main index.php or includes/config.php files that contain 'AutoHoster' or 'iScripts' in the source code.Affected if The application is present on the server and accessible via web
-
Verify the installed version is 2.4Check the version by reviewing the main PHP files or any version definition file. Look for a version variable or changelog file within the application root or includes directory.Affected if The installed version is exactly 2.4 (or falls within the =2.4 range meaning only this version)
-
Identify vulnerable PHP filesLocate these specific files in the web root: the PHP files that handle tmpid, fname, and id parameters. Check if files like main_smtp.php and others handling file operations exist and are web-accessible.Affected if The vulnerable files (main_smtp.php and those handling tmpid/fname/id parameters) exist and are accessible via the web server
-
Test for directory traversal vulnerabilityReview the application's parameter handling code for tmpid, fname, and id parameters. Look for file include/require/read operations that use these parameters without proper sanitization of ../ sequences.Affected if The code accepts path traversal sequences (../../) in tmpid, fname, or id parameters without validation or uses realpath() to verify the path stays within intended directories
A user is affected if they have iScripts AutoHoster version 2.4 running with web-accessible PHP files that handle tmpid, fname, or id parameters without sanitizing ../ sequences.
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 strict input validation and path sanitization on all file-related parameters - reject requests containing ../ sequences, use realpath() to validate resolved paths stay within intended directories, and apply least-privilege file access controls.
- Consultation3.0 h
- Implementation10.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-7190 — 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-7190 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