WP Film Studio < 1.3.5 - Arbitrary Plugin Activation via CSRF
Description
The WP Film Studio WordPress plugin before 1.3.5 does not have CSRF check when activating plugins, which could allow attackers to make logged in admins activate arbitrary plugins present on the blog via a CSRF attack
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected products
2- WordPress/WP Film Studiodescription
- Range: <1.3.5
Patches
Vulnerability mechanics
Root cause
"Missing CSRF nonce check on the plugin activation functionality allows an attacker to forge requests on behalf of an authenticated administrator."
Attack vector
An attacker crafts a malicious page or link that, when visited by a logged-in WordPress administrator, silently submits a forged request to the WP Film Studio plugin's activation endpoint [ref_id=1]. Because the plugin lacks a CSRF check [CWE-352], the administrator's browser sends the request with their valid session cookies, causing an arbitrary plugin already present on the blog to be activated without the administrator's knowledge or consent [ref_id=1]. The attack requires no special network position beyond the ability to deliver the crafted payload to the victim administrator.
Affected code
The advisory does not specify the exact file or function name within the WP Film Studio plugin that handles plugin activation without a CSRF check [ref_id=1]. The vulnerable code is present in versions before 1.3.5.
What the fix does
The advisory states the vulnerability is fixed in version 1.3.5 of the WP Film Studio plugin [ref_id=1]. No patch diff is provided in the bundle, but the remediation would involve adding a CSRF nonce check (e.g., using WordPress's `wp_nonce_field()` and `check_admin_referer()`) to the plugin activation handler so that the request is only processed when accompanied by a valid, user-specific nonce [ref_id=1].
Preconditions
- authThe victim must be logged in as a WordPress administrator.
- networkThe attacker must be able to deliver a crafted link or page to the victim (e.g., via email, social engineering, or embedding on a third-party site).
- inputThe target plugin to be activated must already be present on the WordPress blog (installed but not activated).
Reproduction
1. Ensure a target plugin (e.g., `malicious-plugin/malicious-plugin.php`) is installed on the WordPress site but not activated. 2. Craft an HTML page that auto-submits a form to `wp-admin/plugins.php?action=activate&plugin=malicious-plugin/malicious-plugin.php&_wpnonce=<valid_nonce>` — however, because the WP Film Studio plugin lacks its own CSRF check, the attacker may instead target the plugin's own activation AJAX endpoint if one exists. 3. Lure a logged-in administrator to visit the crafted page. 4. The arbitrary plugin becomes activated without the administrator's consent [ref_id=1].
Generated on May 26, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
1- wpscan.com/vulnerability/95a6a11e-da5d-4fac-aff6-a3f7624682b7mitreexploitvdb-entrytechnical-description
News mentions
0No linked articles in our index yet.