CVE-2011-3811
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 · uneditedTomatoCart 1.1.3 allows remote attackers to obtain sensitive information via a direct request to a .php file, which reveals the installation path in an error message, as demonstrated by templates/system/offline.php and certain other files.
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 confidenceTomatoCart 1.1.3 contains an information disclosure vulnerability where directly requesting certain PHP files (such as templates/system/offline.php) causes the application to reveal the installation path in error messages. This path disclosure could assist attackers in reconnaissance efforts for subsequent attacks.
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= 1.1.3CVSS 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.
-
Identify TomatoCart installation and versionCheck for TomatoCart installation directory and locate version file, or access admin panel to view version information. Common paths include /catalog/ or root web directory. Look for a version.php file or check the admin dashboard for version display.Affected if The installed version is exactly 1.1.3 (note: this CVE affects only this specific version)
-
Verify vulnerable file existsCheck if the file templates/system/offline.php exists in the web root. Use file system access or attempt to access it via HTTP request.Affected if The file templates/system/offline.php exists in the web-accessible directory
-
Test for path disclosure via direct PHP requestSend an HTTP request directly to templates/system/offline.php (or similar PHP files in templates/system/) and examine the error output for installation path disclosure.Affected if Error messages returned by the server contain full server file system paths (e.g., /var/www/html/tomatocart/...)
-
Check PHP error display configurationCheck php.ini for display_errors setting, or create a PHP info file to verify if error reporting is enabled. Can also test by triggering a PHP error and observing if errors are shown.Affected if display_errors is set to On in PHP configuration
A user is affected if they have TomatoCart version 1.1.3 installed AND direct access to templates/system/offline.php is allowed AND PHP error display is enabled, resulting in full installation path disclosure in error messages.
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 dataDisable PHP error display via php.ini (display_errors=Off) or configure the web server to prevent direct access to the vulnerable PHP files and return a 403 Forbidden response instead.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-3811 — 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-2011-3811 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