CVE-2026-12040fs-code FS Poster server-side request forgery
CVE-2026-12040 is a server-side request forgery in fs-code FS Poster, rated medium (6.4 on CVSS 3.1).
Why this priority: Medium severity, with no exploitation signal.
Published · Updated · NVD status: Deferred
What it is
The server can be made to fetch an address of the attacker's choosing, including internal services and cloud metadata endpoints.
How it is reached
An attacker can exploit it over the network, with an ordinary user account, and nobody has to click anything.
What an attacker gains
The direct impact is limited: partial access to data or a partial outage. In practice, this kind of flaw lets an attacker make the server send requests into internal networks or cloud metadata. The damage can spread past the vulnerable component into others.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- No fixed version is listed yet. Find every place fs-code FS Poster runs, watch the references for a fix, and plan a replacement if it is no longer supported.
- While there is no fix, review who holds accounts that can reach it.
Description from NVD
The FS Poster - WordPress Social media Auto Poster & Scheduler [Facebook, Instagram, Twitter, Pinterest] plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 8.0.1 via the 'site_url' parameter. This makes it possible for authenticated attackers, with subscriber-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. The Guzzle HTTP client is instantiated with TLS certificate verification disabled and redirect following enabled by default, allowing redirect-based SSRF bypasses and enabling internal port scanning via distinguishable server responses.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- WordPress sites and their plugins. Plugins run inside the site with its database access, and many sites are public.
- Services that fetch URLs or call other hosts for a caller. The flaw sits between the application and the internal network behind it.
Trust boundaries in play
- Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
- Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
- Between the application and the internal network behind it. An attacker who crosses it can make the server send requests into internal networks or cloud metadata.
Questions to answer about your own systems
- Where does fs-code FS Poster run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.