CVE-2011-3767
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 · uneditedosCommerce 3.0a5 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 redirect.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 confidenceosCommerce 3.0a5 contains an information disclosure vulnerability where direct requests to certain PHP files (such as redirect.php) cause the application to reveal the full installation path in error messages. This path disclosure can aid 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= 3.0a5CVSS 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.
-
Verify osCommerce versionCheck your installed osCommerce version by reviewing version files in the application root directory, typically in a version.php file or similar metadata file included with the installation.Affected if The installed version is osCommerce 3.0a5 exactly.
-
Check PHP display_errors settingLocate your php.ini configuration file (or check via phpinfo()) and verify whether display_errors is set to On or Off.Affected if display_errors is enabled (set to On), which allows error messages to be displayed.
-
Test redirect.php for path disclosureSend a direct HTTP request to the redirect.php file in your osCommerce installation (for example, visit http://yourdomain.com/catalog/redirect.php in a browser or via curl).Affected if The response contains the full server file system path (such as /var/www/html/oscommerce/) in any error message or warning.
-
Check custom error handlingReview your application's error handling configuration, typically in includes/application_top.php or similar bootstrap files, to determine if custom error handlers are defined that suppress path disclosure.Affected if No custom error handling exists and error messages are allowed to display raw PHP errors containing file paths.
You are affected if you are running osCommerce 3.0a5 with PHP display_errors enabled and direct requests to redirect.php reveal the installation path 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 dataConfigure PHP to disable display_errors in production environments and implement custom error handling that does not expose file system paths. Alternatively, apply any available vendor patches for osCommerce 3.0a5.
- 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-3767 — 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-3767 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