CVE-2011-1135
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 · uneditedCross-Site Scripting (XSS) in Xinha, as included in the Serendipity package before 1.5.5, allows remote attackers to execute arbitrary code in plugins/ExtendedFileManager/manager.php and plugins/ImageManager/manager.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 confidenceCross-Site Scripting (XSS) vulnerability in the Xinha WYSIWYG editor plugin included with Serendipity CMS. The vulnerability exists in plugins/ExtendedFileManager/manager.php and plugins/ImageManager/manager.php, allowing remote attackers to inject malicious scripts through these file manager interfaces.
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.5.5CVSS 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
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 Serendipity installationCheck for the presence of Serendipity CMS by looking for the main index.php file or serendipity_config_local.inc.php in the web root directory.Affected if Serendipity CMS is present on the server.
-
Determine Serendipity versionOpen serendipity/include/functions_config.inc.php and look for a line defining the version, typically showing something like $serendipity['version'] = 'x.x.x' or check the serendipity/docs/CHANGELOG file for the installed version.Affected if The installed version is earlier than 1.5.5 (for example, 1.5.4, 1.5.3, 1.4.x, etc.).
-
Locate Xinha plugin directoryNavigate to the plugins directory within the Serendipity installation and look for folders named 'ExtendedFileManager' and 'ImageManager' which are part of the Xinha WYSIWYG editor plugin.Affected if Both the ExtendedFileManager and ImageManager plugin directories exist in the plugins folder.
-
Verify vulnerable manager.php files existCheck that the files plugins/ExtendedFileManager/manager.php and plugins/ImageManager/manager.php are present on the filesystem.Affected if Both manager.php files exist in their respective Xinha plugin subdirectories.
-
Confirm Xinha plugin is activeLog into the Serendipity admin panel, navigate to the Plugins or Configuration section, and verify whether the Xinha WYSIWYG editor is enabled as the default or active editor.Affected if The Xinha editor is enabled and active in the Serendipity configuration.
A Serendipity installation is affected if it is running a version earlier than 1.5.5 AND has the Xinha plugin with ExtendedFileManager/ImageManager directories present AND the Xinha editor is enabled.
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 data1.5.5
Update Serendipity to version 1.5.5 or later which includes the patched Xinha plugin. If upgrading is not feasible, disable or remove the ExtendedFileManager and ImageManager plugins from the Xinha installation.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-1135 — 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-1135 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