CVE-2014-10385
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 memphis-documents-library plugin before 3.0 for WordPress has XSS via $_REQUEST.
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 confidenceThe memphis-documents-library WordPress plugin before version 3.0 contains a Cross-Site Scripting (XSS) vulnerability due to improper handling of user input via the $_REQUEST superglobal. The plugin directly uses unsanitized request parameters, allowing attackers to inject malicious JavaScript through GET or POST parameters.
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< 3.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
- 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 Memphis Documents Library plugin filesCheck your WordPress installation at wp-content/plugins/ for a folder named 'memphis-documents-library', 'memphis-documents', or similar Memphis-related plugin directoryAffected if The plugin folder exists in the plugins directory
-
Identify the installed plugin versionOpen the main plugin PHP file (usually the primary .php file in the plugin folder) and look for the version comment in the plugin header (e.g., 'Version: x.x.x' or 'Version: x.x')Affected if The version listed is below 3.0, or no version is found (which may indicate an older unversioned release)
-
Verify the plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and confirm whether Memphis Documents Library is activatedAffected if The plugin shows as Active and the version is below 3.0
-
Check for vulnerable request parameter handlingInspect the plugin PHP files for direct usage of $_REQUEST, $_GET, or $_POST without sanitization functions (such as esc_html, sanitize_text_field, or esc_attr) - look for patterns like '$_REQUEST["param"]' being echoed or output directlyAffected if Unsanitized superglobal access is found in the plugin code and the plugin version is below 3.0
-
Confirm admin interface exposureAccess the plugin admin pages (typically under Documents or a Memphis menu item in the WordPress admin sidebar) and attempt to submit or modify document-related fieldsAffected if The plugin admin interface is accessible and operational with version below 3.0
You are affected if the Memphis Documents Library plugin is installed, active, and running a version lower than 3.0, with unsanitized $_REQUEST usage present in the plugin code.
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 data3.0
Upgrade the memphis-documents-library plugin to version 3.0 or later, which includes proper input sanitization. Until patched, restrict access to the plugin's admin interface and monitor for suspicious requests containing script tags.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-10385 — 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-10385 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