External risk intelligence

Pay with a Tweet Plugin Arbitrary File Deletion Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-115734

This vulnerability affects a WordPress plugin. WordPress installations are commonly deployed as public-facing web applications accessible via the internet. Since the plugin operates within the web-accessible context of the site, the vulnerable functionality is frequently exposed to the public internet in standard deployment patterns.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability exists in the "Pay with a tweet" WordPress plugin that allows users with low-level access to delete any file on the server, potentially leading to a complete website takeover. This issue stems from the plugin's failure to properly check file paths before deletion and to restrict access to its administrative functions.

  • Low-access users can delete any server file.
  • Affects public-facing websites, enabling full compromise.
  • Confirm if this plugin is in use on our sites.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by initiating a request to a vulnerable WordPress site. If the attacker can trick a user with a low-level role, such as a Subscriber, into performing a specific action within the site's administration area, they can trigger the deletion of arbitrary files. This file deletion can ultimately lead to a complete compromise of the website.

  • Requires low-privilege user access.
  • Triggers file deletion via administration screens.
  • Can result in full site compromise.

Live Threat

Current exploitation, exposure, and threat context

A critical vulnerability exists in the "Pay with a tweet" WordPress plugin that allows authenticated users, even with the lowest privilege role, to delete arbitrary files on the server. This could lead to a complete website compromise under supported conditions.

  • Arbitrary server files.
  • Unrestricted file deletion via administration screens.
  • Potential for full website compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in the "Pay with a tweet" WordPress plugin could allow low-privileged users to delete arbitrary server files, leading to a full site compromise. The first practical step is to identify all WordPress sites using this plugin, confirm their accessibility and business criticality, and then assign ownership for remediation planning.

  • Plugin owners should coordinate remediation.
  • Verify all WordPress sites using the plugin.
  • Plan risk-based remediation actions.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Pay with a tweet WordPress plugin?

The Pay with a tweet plugin is an extension for WordPress websites designed to incentivize content sharing by requiring users to share or tweet about a post before they can access specific download links or gated digital content.

What does CWE-73 mean for CVE-2026-115734?

CWE-73 refers to External Control of File Name or Path. In this context, it means the plugin fails to sanitize or validate file paths provided by users, allowing them to manipulate which files the system deletes.

How is the arbitrary file deletion triggered?

An attacker needs an active account on the WordPress site, even with minimal Subscriber privileges, to access the plugin's administrative screens. It cannot be triggered by unauthenticated visitors who lack an account.

Is my site at risk according to Halo Surface Signal?

Halo Surface Signal notes that since this plugin runs within a web-accessible WordPress environment, the vulnerable administrative functions are often exposed to the public internet, increasing the likelihood of unauthorized interaction.

What should I do first to manage this risk?

Start by auditing your WordPress installations to create an inventory of all sites currently using this specific plugin. Once identified, evaluate the necessity of the plugin and coordinate with site owners to plan for its removal or update.

References