HomeWordPress vulnerabilitiesStream
Stream vulnerabilities
Stream has 5 known vulnerabilities in this database. The most recent published record is dated 7 Aug 2026.
- Known vulnerabilities
- 5
- Active installs
- 70,000+
- Latest version
- 4.4.0
- Last updated
- 31 Aug 2026
- Most recent
- 7 Aug 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Broken access control CVE-2026-11907 | Medium 6.5 | Up to 4.2.0 | Fixed in a later version (latest 4.4.0) | 7 Aug 2026 |
| Server-side request forgery (SSRF) CVE-2024-13879 | Medium 5.5 | Up to 4.0.2 | Fixed in a later version (latest 4.4.0) | 17 Feb 2025 |
| Cross-site request forgery (CSRF) CVE-2024-7423 | High 8.8 | Before 4.0.2 | Fixed in 4.0.2 | 13 Sep 2024 |
| Security weakness CVE-2022-4384 | Medium 6.5 | Before 3.9.2 | Fixed in 3.9.2 | 6 Feb 2023 |
| SQL injection CVE-2021-24772 | High 8.8 | Before 3.8.2 | Fixed in 3.8.2 | 17 Nov 2021 |
Read the published descriptions
- CVE-2026-11907, 7 Aug 2026
- The Stream plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.2.0. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to access all Stream activity records via the Heartbeat API. CVE record
- CVE-2024-13879, 17 Feb 2025
- The Stream plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 4.0.2 due to insufficient validation on the webhook feature. This makes it possible for authenticated attackers, with administrator-level access and above, to make web requests to arbitrary locations originating from the web application which can be used to query and modify information from internal services. CVE record
- CVE-2024-7423, 13 Sep 2024
- The Stream plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.0.1. This is due to missing or incorrect nonce validation on the network_options_action() function. This makes it possible for unauthenticated attackers to update arbitrary options that can lead to DoS or privilege escalation via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
- CVE-2022-4384, 6 Feb 2023
- The Stream WordPress plugin before 3.9.2 does not prevent users with little privileges on the site (like subscribers) from using its alert creation functionality, which may enable them to leak sensitive information. CVE record
- CVE-2021-24772, 17 Nov 2021
- The Stream WordPress plugin before 3.8.2 does not sanitise and validate the order GET parameter from the Stream Records admin dashboard before using it in a SQL statement, leading to an SQL injection issue. CVE record
What to do if you run Stream
If you run Stream, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Stream vulnerabilities
Free. We email you when a new vulnerability is published for Stream, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.