CVE-2026-12040: FS Poster (WordPress plugin) · Server-Side Request Forgery
Affects FS Poster (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 6.4 Medium.
Data as of 18 Nov 2026, 11:51 UTC
Thin evidence
One scorer or none| CNA (Wordfence) | CVSS 3.1 | 6.4 |
|---|
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| fs-codeFS Poster - WordPress Social media Auto Poster & Scheduler [Facebook, Instagram, Twitter, Pinterest] | Affected
| Fixed in– |
AI-suggested
Users should restrict plugin access to trusted users only and monitor for suspicious activity. Since the vulnerability requires authenticated access, minimizing user privileges and reviewing user roles can reduce risk. Check the vendor's advisory or plugin updates regularly for any forthcoming official fixes.
Description
FS Poster - WordPress Social media Auto Poster & Scheduler plugin versions up to 8.0.1 contain a Server-Side Request Forgery (SSRF) vulnerability via the 'site_url' parameter. Authenticated users with subscriber-level access or higher can exploit this to make arbitrary web requests from the server, potentially accessing or modifying internal services. The vulnerability is worsened by the Guzzle HTTP client being configured with TLS verification disabled and automatic redirect following enabled, allowing SSRF bypasses and internal port scanning.