Search
Search Results (2 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-11602 | 2 Fs-code, Wordpress-extensions | 2 Fs Poster - Wordpress Social Media Auto Poster & Scheduler [facebook, Instagram, Twitter, Pinterest], Fs Poster | 2026-11-18 | 5.3 Medium |
| 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. | ||||
| CVE-2026-12040 | 2 Fs-code, Wordpress-extensions | 2 Fs Poster - Wordpress Social Media Auto Poster & Scheduler [facebook, Instagram, Twitter, Pinterest], Fs Poster | 2026-11-18 | 6.4 Medium |
| 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. | ||||
Page 1 of 1.