dbcve.org
NeosenseWordPress extension · Dynamicpress

CVE-2016-10954

CRITICAL · 9.8 CVSS v3.1 Published 2019-09-13
Fix available
A fix is available. Upgrade to 1.8 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The Neosense theme before 1.8 for WordPress has qquploader unrestricted file upload.

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 confidence

The Neosense WordPress theme before version 1.8 contains an unrestricted file upload vulnerability in the qquploader component. This allows unauthenticated attackers to upload arbitrary files, including malicious PHP scripts, potentially leading to remote code execution on the affected WordPress installation.

MitigationUpdate the Neosense theme to version 1.8 or later to patch the vulnerability. If immediate updating is not possible, consider disabling the theme, removing the qquploader functionality, or implementing web application firewall rules to block malicious file uploads.

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
NeosenseWordPress extension
Affected:< 1.8

CVSS 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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Neosense theme version
    Locate the Neosense theme folder in wp-content/themes/ and check the style.css file for the 'Version:' header, or check theme config files for version definitions
    Affected if The installed version is below 1.8 (e.g., 1.7, 1.6, etc.) or if the version cannot be determined but the theme is present
  2. Verify qquploader component exists
    Search the theme directory for files or folders named 'qquploader' or containing 'qq' file uploader code - check both the main theme folder and any included libraries subdirectories
    Affected if The qquploader component directory or files are present in the theme
  3. Check upload endpoint accessibility
    Examine the qquploader PHP files to identify the upload handler endpoint, then verify if the upload functionality can be accessed without authentication by reviewing the code for capability checks or include statements
    Affected if The upload handler accepts requests without requiring authentication (no current_user check or similar) or is directly accessible via web request
  4. Inspect upload directories for suspicious files
    Check wp-content/uploads/ and any custom upload paths defined by the theme for recently added files, particularly looking for .php, .phtml, or other executable extensions that do not match expected media types
    Affected if Unexpected PHP files, shell scripts, or other potentially malicious executables are found in upload directories, especially if created recently or by unknown users

A user is affected if the Neosense theme version is below 1.8 AND the qquploader component is present and accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 1.8 or later
Fixed in 1.8
Interim mitigation

Update the Neosense theme to version 1.8 or later to patch the vulnerability. If immediate updating is not possible, consider disabling the theme, removing the qquploader functionality, or implementing web application firewall rules to block malicious file uploads.

Recommended fix High confidence

Neosense 1.8

  1. 1. Back up your WordPress site and database before making any changes
  2. 2. Download the Neosense theme version 1.8 or later from the official theme source
  3. 3. Navigate to Appearance > Themes in WordPress admin dashboard
  4. 4. Deactivate the current Neosense theme
  5. 5. Upload and activate the updated Neosense theme (version 1.8 or higher)
  6. 6. Verify the qquploader functionality works correctly after the upgrade
  7. 7. Test that the file upload functionality now properly validates and restricts file types

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Neosense Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-10954 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-10954 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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