External risk intelligence

Snazzy Social Media Feed Arbitrary File Upload Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-110002

The vulnerability exists in a WordPress plugin, which is typically deployed as a public-facing web application. Because the affected script is directly reachable via a web request, it represents a commonly exposed component of an internet-facing website.

Unrestricted File Upload

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 vulnerability has been identified in a WordPress plugin, specifically the Snazzy Social Media Feed plugin, that allows for arbitrary file uploads. This issue could enable unauthorized code execution on affected systems. The main concern is to confirm if this plugin is in use within our organization and to what extent it might be exposed.

  • Attackers can upload malicious files.
  • Confirms plugin relevance and potential exposure.
  • Assess and mitigate usage of this plugin.

Attack Path

How an attacker could exploit the issue

An attacker can upload a malicious file to a WordPress site by leveraging a vulnerability in the Snazzy Social Media Feed plugin. This is possible because the plugin's `save-to-cache.php` script, which is accessible without needing to load WordPress fully, fails to properly check for authorization or verify the input. By manipulating a parameter, an attacker can cause the script to write an executable PHP file to the server, which can then be run remotely.

  • Attacker uploads malicious file directly.
  • Vulnerable script processes unverified input.
  • Allows remote code execution.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an attacker to upload and execute arbitrary PHP code on a WordPress site by exploiting the Snazzy Social Media Feed plugin's `save-to-cache.php` script. This script, which is directly accessible without WordPress loading, lacks proper security checks and sanitizes user input insufficiently, enabling the creation of executable files.

  • Website files and server access.
  • Authenticated users uploading malicious files.
  • Complete server takeover.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Snazzy Social Media Feed WordPress plugin's arbitrary file upload vulnerability requires immediate attention from teams managing WordPress instances. The first step is to identify all deployments, determine their exposure and criticality, and then assign ownership for remediation.

  • WordPress administrators and platform owners.
  • Verify WordPress sites using the affected plugin.
  • Plan vendor-coordinated updates and controls.

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 Snazzy Social Media Feed plugin?

It is a WordPress extension designed to display social media content on websites. It functions by caching feeds locally to improve performance. The plugin includes a specific script, save-to-cache.php, intended to manage these cached data files automatically.

What does Arbitrary File Upload mean for CVE-2026-110002?

This vulnerability falls under the Unrestricted Upload of File with Dangerous Type (CWE-434) weakness class. It means the plugin fails to verify the content or type of files being saved. Because the system treats user-provided input as safe, an attacker can upload a file containing malicious instructions that the server then executes.

How is this vulnerability triggered?

An attacker triggers the flaw by sending a specifically crafted request to the save-to-cache.php script. The vulnerability exists because this script operates independently of WordPress security checks like authentication or nonces. Simply visiting the site normally does not trigger the bug; the attacker must intentionally send a crafted pluginURL parameter to the script.

Is my website at risk from this vulnerability?

According to Halo Surface Signal, this vulnerability is likely relevant if you run the plugin on an internet-facing website. Because the vulnerable script is directly reachable via a web request without needing to load the full WordPress environment, it creates a publicly accessible path for potential exploitation.

What should I do to secure my WordPress site?

First, locate all WordPress instances in your environment to determine if the Snazzy Social Media Feed plugin is active. If found, assess your site's exposure and verify the plugin version. Prioritize updating the plugin to a patched version once provided by the vendor, or disable and remove the plugin entirely if a secure update is not available.

References