← WordPress Vulnerabilities
WordPress security by component

WP Social Ninja

WP Social Ninja is a WordPress component with 4 published CVE records in this archive. The latest tracked vulnerability was published Jul 23, 2026; the highest CVE/CNA score is 6.5.

Plugin slug: wp-social-reviews

CVE-2026-65521: WP Social Ninja: A security weakness

WP Social Ninja is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is n/a through 4.3.0.

PublishedJul 23, 2026
Known safe version4.3.1
Safe version
Jul 23, 2026 CVE-2026-65521
WP Social Ninja: A security weakness
WP Social Ninja is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is n/a through 4.3.0.
4.3.1
CVE5.3
NVDPending
Dec 18, 2025 CVE-2025-64375
WP Social Ninja: A security weakness
WP Social Ninja 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
CVE6.5
NVDPending
Dec 17, 2025 CVE-2025-13880
WP Social Ninja – Embed Social Feeds, Customer Reviews, Chat Widgets (Google Reviews, YouTube Feed, Photo Feeds, and More): A security weakness
WP Social Ninja – Embed Social Feeds, Customer Reviews, Chat Widgets (Google Reviews, YouTube Feed, Photo Feeds, and More) is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation.
See mitigation notes
CVE6.5
NVDPending
Dec 02, 2025 CVE-2025-13007
WP Social Ninja – Embed Social Feeds, Customer Reviews, Chat Widgets: Cross-site scripting
WP Social Ninja – Embed Social Feeds, Customer Reviews, Chat Widgets 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
NVDPending