CVE-2014-3845
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 request forgery (CSRF) vulnerability in the TinyMCE Color Picker plugin before 1.2 for WordPress allows remote attackers to hijack the authentication of unspecified users for requests that change plugin settings via unknown vectors. NOTE: some of these details are obtained from third party information.
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 confidenceCross-site request forgery (CSRF) vulnerability in the TinyMCE Color Picker plugin for WordPress. The plugin lacks proper nonce validation on settings change requests, allowing attackers to craft malicious pages that trick authenticated administrators into submitting unintended plugin configuration changes.
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.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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 TinyMCE Color Picker plugin installationNavigate to WordPress admin > Plugins and look for 'Tinymce Color Picker' or 'TinyMCE Color Picker' in the installed plugins listAffected if Plugin is present in the WordPress installation
-
Identify installed plugin versionClick on the plugin in the WordPress plugins list to view its details, or check the plugin header in its main PHP file (typically in /wp-content/plugins/tinymce-color-picker/ or similar)Affected if Version is 1.1 or lower, or version cannot be determined
-
Verify plugin is activeIn WordPress admin > Plugins, confirm the TinyMCE Color Picker plugin is activatedAffected if Plugin is activated and running on the site
-
Check for anti-CSRF protection in plugin codeExamine the plugin settings form handling code (usually in the main plugin PHP file) for nonce validation using functions like wp_verify_nonce, check_admin_referer, or nonces in formsAffected if No nonce verification found in settings change handlers, or plugin code lacks CSRF token validation
The environment is affected if the TinyMCE Color Picker plugin is installed with version 1.1 or lower and lacks proper nonce validation on its settings forms.
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 dataUpdate TinyMCE Color Picker plugin to version 1.2 or later, which should include proper anti-CSRF token validation. If no update is available, implement nonce verification on all plugin settings forms and AJAX actions.
- Consultation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3845 — 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-2014-3845 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