CkeditorWordPress extension · Cksource
CVE-2015-9349
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 · uneditedThe ckeditor-for-wordpress plugin before 4.5.3.1 for WordPress has reflected XSS in the "built-in (old)" file browser.
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 confidenceA reflected cross-site scripting (XSS) vulnerability exists in the ckeditor-for-wordpress plugin versions prior to 4.5.3.1. The vulnerability is located in the plugin's built-in (old) file browser component, where user-supplied input is reflected back without proper sanitization, allowing arbitrary JavaScript execution in the context of the user's browser.
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
CkeditorWordPress extension
< 4.5.3.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
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/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.
-
Locate the ckeditor-for-wordpress plugin installationCheck the wp-content/plugins/ directory for a folder named ckeditor-for-wordpress, ckeditor, or similar. Confirm the plugin files are present on the server.Affected if The plugin folder exists in the WordPress plugins directory.
-
Identify the installed plugin versionOpen the plugin's main PHP file or readme.txt and locate the version number in the file header comment. Compare this version to 4.5.3.1.Affected if The installed version is lower than 4.5.3.1.
-
Determine if the built-in file browser is enabledCheck the plugin configuration settings within the WordPress admin panel, or inspect the plugin configuration file for settings related to the file browser (such as filebrowserBrowseUrl, filebrowserUploadUrl, or similar parameters).Affected if The built-in/old file browser component is enabled and accessible.
-
Verify the file browser is reachable via web requestAttempt to access the file browser endpoint directly (typically found in the plugin's filemanager directory). Common paths include /wp-content/plugins/ckeditor-for-wordpress/ckeditor/plugins/filemanager/ or similar paths under the plugin directory.Affected if The file browser endpoint returns a valid response and accepts user-supplied input.
A user is affected if the ckeditor-for-wordpress plugin is installed with a version lower than 4.5.3.1 AND the built-in file browser component is enabled and accessible.
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 data4.5.3.1
Update the ckeditor-for-wordpress plugin to version 4.5.3.1 or later. Until the patch can be applied, disable the built-in file browser and use an alternative file upload mechanism.
Fix this in Ckeditor
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9349 — 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-2015-9349 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