sales@hackhalt.com

Home / Threats / CVE-2026-13158

Everest Toolkit - Improper Input Validation (CVE-2026-13158)

CVE-2026-13158

The Everest Toolkit WordPress plugin through 1.2.3 does not validate the type of files uploaded during demo-content import (the WordPress file-type test is disabled), allowing high-privilege users (Administrator by default, including non-super-admin site administrators on multisite) to upload executable PHP files to the uploads directory.

CVE-2026-13158

HIGH CVSS 7.2 Published 2026-08-01 Updated 2026-08-26
AI Risk Elevated (66/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P3 Priority
Severity Band HIGH
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Affected Components 1
Reference Links 1
AI Risk Engine Elevated (66/100)
Exploitability Medium
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-08-01 CVE published and first recorded in the threat feed.
  2. 2026-08-26 Record updated with latest vulnerability metadata.
  3. 2026-08-07 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 64 days ago

AI enriched 64 days ago (2026-08-07 00:31 UTC)

Technical Summary

The Everest Toolkit WordPress plugin through 1.2.3 does not validate the type of files uploaded during demo-content import (the WordPress file-type test is disabled), allowing high-privilege users (Administrator by default, including non-super-admin site administrators on multisite) to upload executable PHP files to the uploads directory.

Potential Impact

Severity is HIGH (CVSS 7.2). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as Medium based on severity and technical exposure profile.

Primary risk drivers: severity and technical exposure profile

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 66/100 (Elevated, Medium) with priority P3 Priority. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Everest Toolkit PLUGIN · everest-toolkit Affected: >= 0, <= 1.2.3 Fixed version not specified

References

What to do about this

Patch on your next cycle Worth fixing, but not ahead of other work.

Fix it

Update Everest Toolkit to the latest available version.

Where the vendor has not published a fix yet, disable the plugin until they do.

Cannot update today? Request / payload inspection (WAF) in Hack Halt ProSecure blocks this class of attack before WordPress processes the request.

Inspect request parameters and bodies for injection, traversal and file-inclusion payloads, and refuse the request rather than logging it.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs Everest Toolkit, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs Everest Toolkit.

How do I fix it?

Update Everest Toolkit to the latest available version. Where the vendor has not yet published a fix, remove or disable the plugin until they do. Until you can update, Request / payload inspection (WAF) in Hack Halt ProSecure contains this class of attack at the request layer.

What can an attacker actually do?

This is a Improper Input Validation flaw. An attacker who exploits it can submit values the application never expected, with effects that vary by feature.