WooCommerce Accordion Panel CVE-2025-11722
HIGHAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Contributor-level account
-
DeliveryUpload PHP payload to server
-
ExploitInsert crafted categoryaccordionpanel shortcode
-
ExecutionTrigger local file inclusion in include logic
-
ImpactExecute arbitrary PHP code
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V5 - File Handling File inclusion prevention, allowlisting
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Command and Control The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated WordPress account with Contributor-level privileges or higher (per CVSS PR:L) and the ability to render the 'categoryaccordionpanel' shortcode, which that role can do. The plugin 'Woocommerce Category and Products Accordion Panel' (versions ≤ 1.0) must be installed and active. Local File Inclusion of arbitrary existing .php files is possible under these conditions; however, escalation to arbitrary code execution additionally requires that an attacker-controlled .php file can be placed on the server (the description scopes RCE to 'cases where .php file types can be uploaded and included'). Limiting factors: the authentication requirement (no anonymous access), the need to stage an includable PHP file for full RCE (reflected as AC:H), and dependence on sites that actually grant untrusted Contributor accounts - single-administrator installations face substantially lower practical risk. |
| Impact | This is a moderate-priority issue rather than a top-tier emergency, and the signals are largely consistent. The CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:N, C:H/I:H/A:H) scores 7.5 (High): remotely reachable but gated by two meaningful factors - authentication at Contributor level (PR:L) and high attack complexity (AC:H), reflecting that full code execution requires the additional ability to get a .php file onto the server to then include. The CWE-98 (PHP file inclusion) mapping and the trac references to the vulnerable include logic corroborate the LFI mechanism. EPSS is low at 0.61% (48th percentile), there is no CISA KEV listing, and no public exploit is referenced, so there is no evidence of active or widespread exploitation. The primary caveat: impact is rated C:H/I:H/A:H, which assumes the LFI can be chained to execute attacker-controlled PHP - the description explicitly notes code execution occurs 'in cases where .php file types can be uploaded and included,' so on sites that do not permit PHP upload the realistic impact is closer to local file disclosure than full RCE. Risk is therefore real for multi-author WooCommerce sites where untrusted Contributor accounts exist, but modest for single-admin deployments. |
| Exploit ScenarioDerived | An attacker who holds (or registers/phishes their way into) a Contributor-level account on a WordPress site running this plugin embeds the 'categoryaccordionpanel' shortcode with a crafted path parameter to force the plugin to include a local .php file. By first uploading a PHP payload (e.g., disguised in the media/uploads directory) and then including it via the shortcode, they execute arbitrary PHP in the site's context. No public proof-of-concept is referenced at the time of analysis, and the high attack complexity reflects the need to stage an includable PHP file. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Local file inclusion in the WooCommerce Category and Products Accordion Panel plugin (versions up to and including 1.0) allows authenticated attackers with Contributor-level access or higher to include and execute arbitrary local .php files via the 'categoryaccordionpanel' shortcode. While file inclusion itself can lead to information disclosure or bypassing access controls, full remote code execution requires the attacker to first place an attacker-controlled .php file on the server, which raises the attack complexity. No public exploit code was identified at time of analysis, and EPSS is low at 0.61% (48th percentile), so this is a moderate-priority issue rather than an emergency; it is not confirmed actively exploited.
RemediationAI
No vendor-released patch was identified at time of analysis, so the primary mitigation is to disable or uninstall the WooCommerce Category and Products Accordion Panel plugin (versions ≤ 1.0) until a fixed version is available; removing the plugin eliminates the vulnerable shortcode entirely and is the safest action, at the cost of losing the accordion panel functionality. If the plugin must remain active, restrict the ability to create or edit content with the 'categoryaccordionpanel' shortcode to fully trusted roles by adjusting WordPress capabilities and auditing all Contributor-and-above accounts. Site operators should also prevent untrusted users from uploading .php files by enforcing strict file type restrictions and disabling any upload features that accept executable extensions. A web application firewall can block path traversal sequences (e.g., '../') in shortcode attributes as a temporary compensating control, but such rules may be bypassed by encoding and should not replace removal. Consult the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/55315ba1-cbb8-4ce1-96c6-30a02611ba47?source=cve for updates and any newly released patch version.
Affected ProductsAI
The WooCommerce Category and Products Accordion Panel plugin for WordPress is affected in all versions up to and including 1.0 (plugin slug 'accordion-panel-for-category-and-products'). No CPE data was provided, but the vendor advisory from Wordfence and the WordPress plugin Trac repository confirm the affected code, with specific references to the files include/abstract.php and include/categoryaccordionpanel.php at tag 1.0. Sites running the plugin are only vulnerable if the plugin is active and if untrusted users hold Contributor-level privileges or higher.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is an instance of CWE-98, improper control of filename for include/require statement in PHP programs, which in this case manifests as a local file inclusion rather than remote file inclusion. The plugin's shortcode handler 'categoryaccordionpanel' passes a user-supplied parameter to a PHP include or require construct without adequate validation or sanitization, as visible in the plugin source files include/abstract.php (line 256) and include/categoryaccordionpanel.php (line 87) for version 1.0. WordPress shortcodes are rendered during content processing, and a Contributor-level user can create posts containing the shortcode, thereby triggering the include. Because the included file must already exist on the server, exploitation escalates to code execution only when an attacker can upload a .php file (for example via a separate vulnerable upload feature), which is why the assessed vector carries AC:H and why practical risk is limited on installations that do not grant untrusted users Contributor accounts.
Know when PHP gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Remote shortcode reachable by a Contributor (AV:N, PR:L); AC:H because full code execution depends on staging an includable PHP file; high C/I/A once PHP inclusion succeeds.
Primary rating from Vendor (wordfence).
CVSS VectorVendor: wordfence
DescriptionCVE.org
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.
Executive ViewAI
The WooCommerce Category and Products Accordion Panel plugin (versions up to and including 1.0) contains a local file inclusion vulnerability that can allow a user with Contributor-level access to include and execute local PHP files, potentially leading to information disclosure or, under specific conditions, remote code execution. No vendor-released patch identified at time of analysis, and no public exploit identified at time of analysis, so while the technical severity is high, the immediate organizational risk is moderate; any site using this plugin should prioritize mitigation to prevent privilege escalation or data exposure.
No vendor-released patch identified at time of analysis. Interim mitigations: deactivate or remove the plugin versions up to and including 1.0; restrict Contributor-level and higher accounts to trusted users; implement WAF rules to block the 'categoryaccordionpanel' shortcode; conduct file integrity monitoring and audit for unauthorized .php files; monitor logs for exploitation attempts.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Local File Inclusion vulnerabilities occur when an application accepts user-controlled input to specify which file should be loaded or executed, typically through functions like PHP's `include()`, `require()`, or `fopen()`.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it
sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not
(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear
The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by
ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C
Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au
Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c
Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB