CVE-2025-49344
Lifecycle Timeline
2Description
Cross-Site Request Forgery (CSRF) vulnerability in reneade SensitiveTagCloud sensitive-tag-cloud allows Stored XSS.This issue affects SensitiveTagCloud: from n/a through <= 1.4.1.
Analysis
Cross-site request forgery (CSRF) vulnerability in reneade SensitiveTagCloud WordPress plugin through version 1.4.1 allows attackers to perform unauthorized actions on behalf of authenticated administrators, potentially combined with stored XSS to inject malicious content. The vulnerability affects all versions up to and including 1.4.1, with no CVSS vector provided, but EPSS data suggests low real-world exploitation probability (0.02% percentile).
Technical Context
The vulnerability stems from missing or insufficient CSRF token validation (CWE-352) in the SensitiveTagCloud WordPress plugin, a tool designed to display tag clouds with sensitivity filtering. WordPress plugins are executed in the context of the WordPress application, which provides CSRF protection mechanisms via nonces that must be properly implemented in all state-changing requests. The combination of CSRF with stored XSS indicates that an attacker could craft a malicious page that tricks an authenticated administrator into visiting it, triggering an unvalidated request that modifies plugin settings or injects malicious JavaScript into the stored tag cloud data. This represents a chain attack where CSRF is the delivery mechanism and stored XSS is the payload, affecting users of the plugin across all WordPress installations where SensitiveTagCloud version 1.4.1 or earlier is active.
Affected Products
The SensitiveTagCloud WordPress plugin by reneade is affected in all versions through 1.4.1. This is a WordPress plugin component distributed via the WordPress plugin repository. The vulnerability impacts any WordPress installation running SensitiveTagCloud version 1.4.1 or earlier where administrators may be targeted by CSRF attacks.
Remediation
Update the SensitiveTagCloud plugin to a version released after 1.4.1. Administrators should immediately upgrade to the latest available version from the WordPress plugin repository. In the interim, administrators should implement WordPress security best practices including enforcing strong passwords, limiting administrator account exposure, and using security plugins that provide additional CSRF protection. Additional details and advisories are available from Patchstack's vulnerability database entry for this plugin.
Priority Score
Share
External POC / Exploit Code
Leaving vuln.today