LiveActive security incident?Get immediate response
CVE Record

CVE-2016-10995: The Tevolution plugin before 2.3.0 for WordPress has arbitrary file upload via single_upload.php or single-...

The Tevolution plugin before 2.3.0 for WordPress has arbitrary file upload via single_upload.php or single-upload.php.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2016-10995 affects the WordPress Tevolution plugin before version 2.3.0. The reported issue is arbitrary file upload through named upload handler files. For a business, the concern is potential website compromise if an exposed site still runs the vulnerable plugin version.

Executive priority

Prioritize verification on public WordPress sites. If vulnerable Tevolution is present, remediate promptly because arbitrary upload flaws can enable serious site compromise, even though exploitation evidence is not provided here.

Technical view

The CVE record describes arbitrary file upload in Tevolution before 2.3.0 via single_upload.php or single-upload.php. The source bundle does not provide CVSS, CWE, authentication requirements, exploit details, or vendor remediation text beyond the affected version boundary.

Likely exposure

Exposure is likely limited to WordPress sites with the Tevolution plugin installed below version 2.3.0. Public internet exposure matters most, but the provided sources do not confirm reachability requirements or authentication context.

Exploitation context

CISA KEV is false in the source bundle. No cited source here confirms active exploitation, exploit availability, or observed attacks. Treat suspicious upload activity as investigation-worthy, not proof of exploitation.

Researcher notes

The public source bundle is sparse. It identifies product, vulnerable version range, and affected upload handler filenames, but omits CVSS, CWE, privileges required, attack complexity, and patch notes. Avoid assuming unauthenticated exploitation without additional vendor evidence.

Mitigation direction

  • Upgrade Tevolution to version 2.3.0 or later where available.
  • Disable or remove Tevolution if it is not business-critical.
  • Check vendor or maintainer guidance for current remediation advice.
  • Review uploaded media and plugin directories for unauthorized files.
  • Ensure backups and restore procedures are current.

Validation and detection

  • Inventory WordPress sites for the Tevolution plugin and exact version.
  • Confirm whether single_upload.php or single-upload.php is present and externally reachable.
  • Review web logs for unexpected requests to those upload handler paths.
  • Inspect upload locations for unexpected executable or recently modified files.
  • Document findings by site, plugin version, and remediation status.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2016-10995 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.