PrestashopCMS
CVE-2011-3796
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 · uneditedPrestaShop 1.4.0.6 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 product-sort.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 confidencePrestaShop 1.4.0.6 contains an information disclosure vulnerability where direct requests to certain PHP files (such as product-sort.php) trigger PHP error messages that reveal the full server installation path. This occurs because these files lack proper include guards or access controls preventing direct execution.
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
PrestashopCMS
= 1.4.0.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
- 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 PrestaShop versionLocate the PrestaShop installation and check the version file (typically config/settings.inc.php or the admin panel footer) to confirm the installed version is 1.4.0.6Affected if The installed version is exactly 1.4.0.6
-
Identify vulnerable PHP filesLocate product-sort.php in the PrestaShop root directory and search for other PHP files in the same directory that may lack include guards (files that can be executed directly without including core initialization files)Affected if Files like product-sort.php exist and can be accessed directly without loading PrestaShop core
-
Test direct access to product-sort.phpSend an HTTP GET request directly to /product-sort.php (or the equivalent path in your installation) from a browser or curl toolAffected if The file responds and displays PHP error messages containing the full server filesystem path
-
Check for path disclosure in errorsExamine the response from direct file access - look for error messages that contain absolute paths such as /var/www or C:\inetpubAffected if Error output reveals the complete server installation path in the error message
You are affected if PrestaShop version 1.4.0.6 is installed AND direct HTTP requests to files like product-sort.php expose the full server filesystem 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 dataRestrict direct access to vulnerable PHP files by adding include guards at the top of each affected file, and configure PHP error handling to log errors without displaying them publicly. Alternatively, upgrade to a patched PrestaShop version.
Fix this in Prestashop
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,032.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-3796 — 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-3796 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