The BlogBuzzTime for WP plugin for WordPress is vulnerable to stored Cross‑Site Scripting when an authenticated administrator edits the plugin’s settings. The flaw stems from insufficient input sanitization and output escaping that allows arbitrary script payloads to be written into the plugin data, which are later rendered when users view the affected page. This can lead to session hijacking, credential theft, defacement, or other damage in the context of the victim’s browser, and the weakness is classified as CWE‑79 with a moderate‑severity CVSS score of 4.4. The vulnerability can be exploited only by users with administrator‑level permissions or higher, and it specifically affects multi‑site WordPress installations where the unfiltered_html capability has been disabled. The plugin has not been listed in CISA’s Known Exploited Vulnerabilities catalog, and no public exploitation has been reported. The EPSS score of <1% indicates a very low current probability of exploitation, but the impact remains significant if an insider attacker gains access. The potential damage is limited to users who view the stored scripts, yet the exploitation path is straightforward for a privileged user: navigate to the plugin’s settings page, input malicious code, store it, and have it executed for subsequent visitors.

The affected product is the BlogBuzzTime for WP plugin developed by gpenverne, all installed versions 1.1 or earlier running on WordPress multi‑site setups where the 'unfiltered_html' feature is disabled. This includes any WordPress installation using the plugin that has admin accounts capable of editing its settings.

The CVSS score of 4.4 denotes moderate severity, and the EPSS score of less than 1% indicates a low likelihood of exploitation at present. The vulnerability requires authenticated admin access, limiting its attack surface to privileged users. Because it is a stored script payload, any user who views the affected page will automatically run the malicious code in their browser context, potentially compromising session state or stealing credentials. Given these characteristics, the risk is moderate but still noteworthy for organizations with large privileged user bases or multi‑site WordPress environments.