WordPress Semrush Content Toolkit 插件 <= 1.1.32 - 跨站请求伪造 (CSRF) 漏洞

A successful CSRF attack could allow an attacker to manipulate the Semrush Content Toolkit on behalf of an authenticated user. This could involve actions like modifying content, changing user settings, or even deleting data. The impact is directly tied to the permissions of the compromised user account. If a user with administrative privileges is targeted, the attacker could gain significant control over the toolkit's configuration and data. While CSRF typically requires social engineering to trick a user into clicking a malicious link, the potential for automated exploitation exists if the attacker can control the user's environment.

Websites utilizing the Semrush Content Toolkit plugin, particularly those with users who have elevated privileges within the toolkit. Shared WordPress hosting environments are also at increased risk, as vulnerabilities in plugins can impact multiple sites.

• wordpress / composer / npm:

grep -r 'semrush-contentshake' /var/www/html/
wp plugin list | grep semrush-contentshake

• generic web:

curl -I https://your-wordpress-site.com/wp-content/plugins/semrush-contentshake/ | grep Content-Security-Policy

1. 2025-12-16Disclosure

   disclosure

活跃安装数

2K小众

插件评分

2.6

需要WordPress版本

5.0+

兼容至

6.8.5

1. 已保留2025-12-15
2. 发布日期2025-12-16
3. 修改日期2026-04-28
4. EPSS 更新日期2026-03-23

The primary mitigation for CVE-2025-68082 is to upgrade the Semrush Content Toolkit to version 1.1.33 or later. If immediate upgrading is not possible, consider implementing stricter input validation and output encoding within the application to reduce the attack surface. Additionally, enabling Content Security Policy (CSP) headers can help prevent the browser from executing malicious scripts from untrusted sources. While a direct WAF rule is unlikely, generic CSRF protection rules might offer some limited defense. After upgrading, verify the fix by attempting a CSRF attack against a test user account and confirming that the attack is blocked.