Skip to content
Fencer Intel
medium 5.3

CVE-2026-11602 json

FS Poster - WordPress Social media Auto Poster & Scheduler [Facebook, Instagram, Twitter, Pinterest] <= 8.0.1 - Missing Authorization to Unauthorized Social App Data Modification via 'fsp_app_redirect' / 'app' Parameters

published 15h ago modified 11h ago also EUVD-2026-128554

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

The FS Poster - WordPress Social media Auto Poster & Scheduler [Facebook, Instagram, Twitter, Pinterest] plugin for WordPress is vulnerable to missing authorization to Unauthorized Social App Data Modification in all versions up to, and including, 8.0.1 This is due to missing authentication, nonce, and capability checks in the `standardFSApp()` function, which is registered on the `wp` action hook and executes on every frontend page load without any login or permission verification. This makes it possible for unauthenticated attackers to insert arbitrary social network app records into the database, or overwrite the OAuth `client_id` and `client_secret` of existing social network connections, by supplying attacker-controlled values via the `fsp_app_redirect` and `app` GET parameters. An attacker can target a specific existing social app record for credential overwrite by supplying matching `social_network` and `slug` values, requiring no knowledge of internal record IDs, which disrupts scheduled social media posts and forces administrators to re-authenticate their connected accounts.

Is CVE-2026-11602 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
13h ago

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected products

  • fs-code FS Poster - WordPress Social media Auto Poster & Scheduler [Facebook, Instagram, Twitter, Pinterest]

Classification

Weakness
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.