← WordPress Vulnerabilities
WordPress security by component

Smash Balloon Social Post Feed

Smash Balloon Social Post Feed is a WordPress component with 4 published CVE records in this archive. The latest tracked vulnerability was published Jan 16, 2023; the highest CVE/CNA score is 6.1.

Plugin slug: smash-balloon-social-post-feed

CVE-2022-4477: Smash Balloon Social Post Feed: Cross-site scripting

Smash Balloon Social Post Feed is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

PublishedJan 16, 2023
Safe version guidanceSee mitigation notes
Safe version
Jan 16, 2023 CVE-2022-4477
Smash Balloon Social Post Feed: Cross-site scripting
Smash Balloon Social Post Feed is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE5.4
NVD5.4
Jan 17, 2022 CVE-2021-25065
Smash Balloon Social Post Feed: Cross-site scripting
Smash Balloon Social Post Feed is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE5.4
NVD5.4
Nov 29, 2021 CVE-2021-24918
Smash Balloon Social Post Feed: A security weakness
Smash Balloon Social Post Feed is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
See mitigation notes
CVE5.4
NVD5.4
Sep 13, 2021 CVE-2021-24508
Smash Balloon Social Post Feed: Cross-site scripting
Smash Balloon Social Post Feed is affected by cross-site scripting. The vulnerable path is reachable without authentication. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE6.1
NVD6.1