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

Back
New CVE Detected

CVE-2026-14484 – Unauthenticated Arbitrary File Deletion (leading to potential RCE) – RapiSafe – Sec

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-14484 is a critical arbitrary file deletion vulnerability affecting the RapiSafe – Secure Multi File Upload for Contact Form 7 WordPress plugin, in all versions up to and including 1.0.4. The flaw stems from insufficient path validation in the plugin’s AJAX file-removal handler, allowing unauthenticated attackers to delete arbitrary files on the web server. Because deletion of critical files (such as wp-config.php) can force a site into a state where an attacker can complete a fresh WordPress installation and gain full control, this issue carries a CVSS v3.1 base score of 9.1 (Critical).

Technical details

  • Root cause: The plugin’s handleAjaxRemoveUpload function (implemented in the plugin’s assets/plugin handler code) fails to properly validate or sanitize the file path supplied via the rsmfcf7_session and file_name request parameters before performing a file deletion operation.
  • Trigger conditions: The AJAX endpoint that handles upload removal relies on a security nonce for request validation; however, this nonce is exposed in publicly-loaded client-side JavaScript, meaning it provides no effective protection against unauthenticated requests.
  • Attack vector: Network-based (AV:N) — an attacker can send a crafted HTTP request directly to the vulnerable AJAX action on any site running the affected plugin, with no authentication or user interaction required.
  • Impact: Successful exploitation allows deletion of arbitrary files on the underlying server. Deleting sensitive files, such as wp-config.php, can trigger the WordPress setup wizard and potentially enable remote code execution and full site takeover.

Affected software

  • RapiSafe – Secure Multi File Upload for Contact Form 7 (WordPress plugin, developed by pietror91) — versions up to and including 1.0.4

Severity

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

Mitigation and recommended actions

  • Immediate: Upgrade RapiSafe – Secure Multi File Upload for Contact Form 7 to a patched version above 1.0.4 as soon as one is released by the vendor. Check the WordPress.org plugin repository for the latest release and changelog before updating.
  • If no patch is available: Deactivate and remove the plugin until a fix is released, since the vulnerable AJAX endpoint is reachable without authentication. As an interim network-level mitigation, block or restrict access to the plugin’s AJAX action (admin-ajax.php requests referencing the RapiSafe upload-removal action) at the WAF or reverse-proxy layer, and ensure regular, isolated backups of wp-config.php and other critical files are maintained to speed recovery in case of exploitation.

References

Are you exposed?

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge