Skip to main content
VulnerabilityPublished

CVE-2026-12040: FS Poster (WordPress plugin) · Server-Side Request Forgery

Affects FS Poster (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.4 Medium.

Data as of 18 Nov 2026, 11:51 UTC

CVSS 3.1 base score
6.4Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.16.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
fs-codeFS Poster - WordPress Social media Auto Poster & Scheduler [Facebook, Instagram, Twitter, Pinterest]Affected
  • <=8.0.1
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.

References

Community reviews

Loading reviews…