Cyber & AI intelligence
Wasteland.
Briefs indexed3476
Issues33
Published Mondays07:30 CT
⚡ Active KEV CVE-2026-110002 2026-10-14

CVE-2026-110002: Critical Arbitrary File Upload in Snazzy Social Media Feed WordPress Plugin

"CVE-2026-110002 is a critical (CVSS 9.8) arbitrary file upload flaw in the Snazzy Social Media Feed WordPress plugin through version 2.5. It can lead to remote code execution."

CVE-2026-110002 is a critical (CVSS 9.8) arbitrary file upload flaw in the Snazzy Social Media Feed WordPress plugin through version 2.5. It can lead to remote code execution.

What Is It

CVE-2026-110002 is an arbitrary file upload vulnerability (CWE-434) in the plugin's standalone save-to-cache.php script. According to the advisory and the referenced source lines, the script can be reached directly without loading WordPress. It also appears to skip WordPress bootstrap, authentication, capability and nonce checks.

The advisory says the only filter applied to the pluginURL parameter is FILTER_SANITIZE_URL. That filter keeps the characters needed to build a valid PHP payload. The value is reportedly written unchanged into cached-content/cached-feed.php, where a single GET request can then run it.

The privilege level an attacker needs is unclear. Wordfence's description says attackers need subscriber-level access or higher. However, the CVSS vector it assigned marks Privileges Required as None, and the same description says the script has no authentication checks. Until this conflict is resolved, defenders should assume the exploitation path described above may work without authentication, and treat it as possibly needing at least a subscriber account.

Why It Matters

CVE-2026-110002 is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. KEV does not confirm active exploitation at this time.

What's Vulnerable

Patch Status

The supplied NVD record does not list a fixed version. It was published on 2026-10-14 with status "Received" and has no CISA required action or remediation deadline.

Until a fixed release is confirmed, administrators running version 2.5 or earlier should check the Wordfence advisory for updates. They should also consider deactivating or removing the plugin. Because the privilege requirement is disputed, the safest approach is to treat exposed installations as reachable by unauthenticated attackers.

Sources