dbcve.org
TelvolutionWordPress extension · Templatic

CVE-2016-10995

CRITICAL · 9.8 CVSS v3.1 Published 2019-09-18
Fix available
A fix is available. Upgrade to 2.3.0 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 Tevolution plugin before 2.3.0 for WordPress has arbitrary file upload via single_upload.php or single-upload.php.

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 Tevolution WordPress plugin before version 2.3.0 contains arbitrary file upload vulnerabilities in single_upload.php and single-upload.php, allowing unauthenticated attackers to upload any file type including malicious PHP scripts that could lead to remote code execution.

MitigationUpdate Tevolution plugin to version 2.3.0 or later to remediate the vulnerability. If the plugin is unused, consider removing it entirely.

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
TelvolutionWordPress extension
Affected:< 2.3.0

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. Check if Tevolution plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Tevolution' or 'Templatic Tevolution' in the list
    Affected if Tevolution plugin appears in the installed plugins list
  2. Identify installed Tevolution version
    In the plugins list, find the Tevolution entry and note the version number displayed below the plugin name, or check the plugin's main PHP file header for 'Version:' tag
    Affected if The installed version is lower than 2.3.0 (e.g., 2.2.9, 2.2.0, etc.)
  3. Verify vulnerable upload files exist
    Check the wp-content/plugins/tevolution/ directory for the presence of single_upload.php and single-upload.php files using FTP, file manager, or command line
    Affected if Either single_upload.php or single-upload.php file exists in the plugin directory
  4. Confirm plugin is active
    In WordPress admin > Plugins, verify whether Tevolution is currently activated. An inactive plugin may still be exploitable if the files are accessible via direct URL
    Affected if Tevolution plugin is active or the vulnerable PHP files are accessible via direct web request

If Tevolution plugin version is below 2.3.0 AND the vulnerable upload files exist in the plugin directory, the environment is affected by this arbitrary file upload vulnerability.

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 2.3.0 or later
Fixed in 2.3.0
Interim mitigation

Update Tevolution plugin to version 2.3.0 or later to remediate the vulnerability. If the plugin is unused, consider removing it entirely.

Recommended fix High confidence

2.3.0 or later

  1. 1. Create a complete backup of the WordPress database and all files
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find the Tevolution plugin in the list
  5. 5. If an update is available, click 'Update Now' to upgrade to version 2.3.0 or later
  6. 6. Alternatively, download the Tevolution plugin version 2.3.0 or newer from a trusted source and upload it via Plugins > Add New > Upload Plugin
  7. 7. After updating, verify the new version number is showing in the plugins list
  8. 8. Test the file upload functionality to confirm the plugin continues to work correctly

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

Fix this in Telvolution Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-10995 — 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-10995 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