Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-81780 – Unauthenticated Arbitrary File Upload (RCE) – Hash Form WordPress Plugin ≤ 1.4.2

Be the first to know when new zero-days emerge:

Summary

CVE-2026-81780 is a critical unauthenticated arbitrary file upload vulnerability in the Hash Form WordPress plugin (developed by hashthemes), affecting all versions up to and including 1.4.2. The flaw allows a remote, unauthenticated attacker to upload arbitrary files to the server, which can lead to remote code execution and full site compromise. It carries the maximum CVSS v3.1 base score of 10.0.

Technical details

  • Root cause: CWE-434, Unrestricted Upload of File with Dangerous Type — the plugin fails to properly validate/restrict the type of files submitted through its upload functionality.
  • Trigger conditions: An attacker submits a file upload request to the vulnerable plugin endpoint without needing any authentication or user interaction.
  • Attack vector: Network (remote), low attack complexity, no privileges required, no user interaction required.
  • Impact: High confidentiality, integrity, and availability impact; a successfully uploaded malicious file (e.g., a PHP script) can be executed on the server, enabling full compromise of the WordPress installation.

Affected software

  • Hash Form (WordPress plugin) by hashthemes, versions <= 1.4.2

Severity

  • CVSS v3.1 Base Score: 10.0 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade the Hash Form plugin to version 1.4.3 or later, where the file upload validation issue is fixed.
  • If immediate patching is not possible: Disable or remove the Hash Form plugin until it can be updated, and restrict/monitor access to plugin upload endpoints (e.g., via a WAF rule blocking unauthenticated multipart/file-upload requests to the plugin’s handlers).
  • Review the server and uploads directory for unexpected or recently added files, particularly executable scripts, to check for prior exploitation.

How IONIX identifies potentially affected assets

IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: /wp-content/plugins/hash-form/

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge