Arbitrary file upload in Snazzy Social Media Feed WordPress plugin
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Code execution
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-434.
Summary
All versions of the Snazzy Social Media Feed plugin for WordPress through 2.5 are affected. The standalone save-to-cache.php script is reachable without loading WordPress and lacks authentication and nonce checks, and the pluginURL parameter is insufficiently sanitized before it is written into a web-executable PHP file (CWE-434). A remote attacker with no privileges can upload files that may be executable, which makes remote code execution possible.
Written with Claude Haiku 5.5 from the sources below · 2026-10-28
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| snazzyplugins | Snazzy Social Media Feed | up to 2.5 | — | No fix listed | CNA |
- Snazzy Social Media Feed Vendorsnazzyplugins Affected up to 2.5 Fixed in — No fix listed CNA
Remediation
The sources list no fixed version for Snazzy Social Media Feed.
Written with Claude Haiku 5.5 from the sources below · 2026-10-28
Timeline
- 2026-10-14 Threatist record created from CVE-2026-110002
- 2026-10-14 Alias added: GHSA-cqr7-6967-pf9v
- 2026-10-16 CISA SSVC decision points changed
References
Other 5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/98dd1333-81ee-4036-a738-03a3f0a0022d?source=cve
- https://plugins.trac.wordpress.org/browser/snazzy-cacheable-facebook-feed/trunk/functions/save-to-cache.php#L70
- https://plugins.trac.wordpress.org/browser/snazzy-cacheable-facebook-feed/trunk/functions/save-to-cache.php#L328
- https://plugins.trac.wordpress.org/browser/snazzy-cacheable-facebook-feed/trunk/functions/save-to-cache.php#L311
- https://plugins.trac.wordpress.org/browser/snazzy-cacheable-facebook-feed/trunk/functions/save-to-cache.php#L315
Sources
- CVE-2026-110002 · CVE Program
- CVE-2026-110002 · NVD
- FIRST EPSS
- GHSA-cqr7-6967-pf9v · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences