# CVE-2026-110002: Snazzy Social Media Feed <= 2.5 - Unauthenticated Arbitrary File Upload via 'pluginURL' Parameter

> Unauthenticated attackers can upload executable PHP files via the pluginURL parameter, leading to remote code execution.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-cqr7-6967-pf9v

## What is CVE-2026-110002?

CVE-2026-110002 is a critical vulnerability in snazzyplugins Snazzy Social Media Feed, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Snazzy Social Media Feed plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and including, 2.5 via the (file scope) function. This is due to missing WordPress bootstrap, authentication, capability, and nonce checks in the standalone save-to-cache.php script, combined with insufficient sanitization of the pluginURL parameter before it is written to a web-executable PHP file. This makes it possible for authenticated attackers, with subscriber-level access and above, to upload files that may be executable, which makes remote code execution possible. The save-to-cache.php script is directly reachable without loading WordPress; FILTER_SANITIZE_URL — the only filter applied to the pluginURL value — preserves the characters required to craft a valid PHP payload, which is then written verbatim into cached-content/cached-feed.php and immediately executable via a single GET request.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2026-110002?


## How do I fix CVE-2026-110002?

No fix has been published for CVE-2026-110002 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-110002 being exploited?

There is no known exploitation of CVE-2026-110002 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-110002 and fix it if it is affected.

What it is: CVE-2026-110002 is a critical vulnerability in snazzyplugins Snazzy Social Media Feed, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-110002 in the wild and no public exploit code.

Affected product: snazzyplugins Snazzy Social Media Feed. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-110002/ (Markdown: https://insights.sbomify.com/CVE-2026-110002/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-110002
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-110002
- OSV: https://osv.dev/vulnerability/CVE-2026-110002

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-110002/
Summaries are generated and may contain mistakes; the official description above is the record.