Search EverythingWordPress extension · Zemanta
CVE-2014-3843
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 Search Everything plugin before 8.1.1 for WordPress allows remote attackers to hijack the authentication of unspecified victims via unknown vectors.
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 request forgery (CSRF) vulnerability in the Search Everything WordPress plugin before version 8.1.1 allows remote attackers to trick authenticated administrators into performing unwanted actions (such as modifying plugin settings) by embedding malicious requests in external sites or emails.
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
Search EverythingWordPress extension
<= 8.1= 7.0.2= 7.0.3= 7.0.4= 8.0CVSS 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.
-
Verify Search Everything plugin is installedLog into WordPress admin panel, navigate to Plugins > Installed Plugins, and locate 'Search Everything' or 'Zemanta Search Everything' in the list of installed plugins.Affected if The plugin does not appear in the installed plugins list, meaning it is not installed and not affected.
-
Confirm the installed version numberIn the WordPress admin Plugins page, find the Search Everything entry and locate the version number displayed beneath the plugin name. Alternatively, inspect the plugin main file (usually search-everything.php in wp-content/plugins/search-everything/) and look for the 'Version' header in the file comment block.Affected if The displayed version matches any of these: 8.1 or earlier, 7.0.2, 7.0.3, 7.0.4, or 8.0.
-
Verify the plugin is activeIn WordPress admin under Plugins > Installed Plugins, check whether Search Everything shows an 'Activate' link (inactive) or 'Deactivate' link (active).Affected if The plugin is active, meaning it is loaded and processing requests, which is required for the CSRF vulnerability to be exploitable.
-
Confirm the exact version matches affected releasesCompare your installed version against the full affected list: <= 8.1, 7.0.2, 7.0.3, 7.0.4, 8.0. Note that version 8.1.1 and later are not affected.Affected if Your version is exactly 8.1 or lower, or matches 7.0.2, 7.0.3, 7.0.4, or 8.0 exactly.
You are affected if the Search Everything plugin is installed, active, and the installed version is 8.1 or earlier, or specifically 7.0.2, 7.0.3, 7.0.4, or 8.0.
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 the Search Everything plugin to version 8.1.1 or later which includes anti-CSRF token validation. Until updated, avoid clicking untrusted links while logged into WordPress admin.
Fix this in Search Everything
Scoped from the published advisory
- Consultation2.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3843 — 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-3843 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