bensibley vulnerabilities and threats

The Independent Analytics WordPress plugin up to version 2.15.0 is vulnerable to stored Cross-Site Scripting (XSS) via the 404 not_found_url tracking parameter. This occurs because the plugin improperly decodes URL-encoded input after URL validation, allowing malicious HTML to be injected and executed in users' browsers. The vulnerability can be exploited without authentication due to a public REST endpoint that accepts signed requests embedded in public page HTML.

The Independent Analytics plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 2.14.9. This is due to a public tracking route at /wp-json/iawp/search that accepts attacker-controlled referrer_url values when the signature matches, combined with a scheduled favicon fetcher that performs unrestricted cURL requests to stored domains. The signature validation is insufficient because the signature is embedded in publicly-accessible JavaScript and the salt is static per site, allowing attackers to extract valid signatures. The favicon downloader uses raw cURL functions without any SSRF protection mechanisms (no localhost blocking, no private network filtering, and does not use WordPress's wp_safe_remote_* functions). This makes it possible for unauthenticated attackers to inject malicious referrer domains into the database and trigger server-side requests to arbitrary hosts including internal services.

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in bensibley Unlimited unlimited allows Stored XSS.This issue affects Unlimited: from n/a through <= 1.45.