CVE-2025-11722
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Woocommerce Category and Products Accordion Panel WordPress plugin versions up to 1.0 contains a Local File Inclusion vulnerability in the 'categoryaccordionpanel' shortcode. Authenticated attackers with Contributor-level access or higher can exploit this to include and execute arbitrary .php files on the server, achieving code execution by leveraging uploaded or existing PHP files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if the plugin is installedInspect the WordPress plugins directory at /wp-content/plugins/ for a folder named 'woocommerce-category-products-accordion-panel', 'wc-category-accordion', or similar variations containing 'accordion' and 'woocommerce' in the name.Affected if The plugin directory exists in the WordPress plugins folder.
-
Identify the installed plugin versionOpen the main plugin PHP file (usually named the same as the plugin folder) or the readme.txt file within the plugin directory and locate the version declaration near the top of the file.Affected if The installed version is 1.0 or any version below the latest patched version.
-
Check for usage of the vulnerable shortcodeSearch the WordPress database or inspect pages/posts for the shortcode [categoryaccordionpanel] or [wc_category_accordion] by querying the wp_posts table or using a plugin like Search Replace Database.Affected if The shortcode [categoryaccordionpanel] is present in any post, page, or custom post type content.
-
Review WordPress user roles with elevated accessNavigate to Users > All Users in the WordPress admin dashboard and identify accounts assigned the Contributor, Author, Editor, or Administrator roles.Affected if There are user accounts with Contributor-level access or higher, which enables authenticated exploitation.
You are affected if the plugin is installed with version 1.0 or below AND the vulnerable shortcode is actively used in your content, allowing an attacker with Contributor-level access to achieve code execution via LFI.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the plugin to the latest version once available, or disable and remove the plugin until a patch is released. Additionally, review user role permissions to ensure only trusted users have Contributor-level or higher access.
- Consultation3.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11722 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-11722 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data