CVE-2011-3804
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 · uneditedSweetRice 0.7.1 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 _plugin/tiny_mce/plugins/advimage/images.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 · moderate confidenceSweetRice 0.7.1 contains an information disclosure vulnerability where directly requesting certain PHP files (such as _plugin/tiny_mce/plugins/advimage/images.php) causes the application to reveal the full installation path in error messages. This path disclosure can aid attackers in mapping the system's directory structure for more targeted follow-up 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= 0.7.1CVSS 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 SweetRice installation versionLocate the SweetRice installation and check the version file or meta information. Common paths include checking the main directory for version indicators, or accessing the admin dashboard version display.Affected if The installed version is exactly 0.7.1
-
Check if vulnerable plugin files existVerify the presence of the _plugin/tiny_mce/plugins/advimage/images.php file (and similar paths like _plugin/tiny_mce/plugins/advlink/images.php) in the web root directory.Affected if These plugin PHP files exist in the installation
-
Test for path disclosure via direct requestSend an HTTP GET request directly to the vulnerable PHP files (e.g., /_plugin/tiny_mce/plugins/advimage/images.php) without proper authentication or parameters. Inspect the response for error messages that reveal full file system paths.Affected if The response contains full server file system paths in error messages
-
Verify PHP error display is enabledCheck the PHP configuration (php.ini) or the SweetRice configuration for error_display or error_reporting settings. Also check if the web server is configured to display PHP errors.Affected if PHP error display (display_errors) is set to On or error reporting is set to show errors
You are affected if SweetRice version 0.7.1 is installed AND the vulnerable plugin PHP files exist AND direct requests to those files reveal full installation paths 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 and logging in production environments, and restrict direct access to plugin directories via web server configuration or .htaccess rules to prevent unauthorized file access.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-3804 — 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-3804 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