dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-11746

HIGH · 8.8 CVSS v3.1 Published 2025-10-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
The XStore theme for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 9.5.4 via theet_ajax_required_plugins_popup() function. This makes it possible for authenticated attackers, with Subscriber-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 confidence

The XStore theme for WordPress contains a Local File Inclusion (LFI) vulnerability in the et_ajax_required_plugins_popup() function affecting all versions up to 9.5.4. Authenticated attackers with Subscriber-level access or higher can exploit this to include and execute arbitrary .php files on the server, leading to code execution.

MitigationUpdate the XStore theme to a version newer than 9.5.4 when a patch becomes available, or implement input validation/sanitization on the file inclusion parameters in the vulnerable function.

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm XStore theme is installed
    Check the wp-content/themes/ directory for the xstore folder, or query the WordPress database: SELECT theme FROM wp_themes WHERE active=1;
    Affected if The xstore theme folder exists and is active in WordPress
  2. Identify the installed XStore theme version
    Open wp-content/themes/xstore/style.css and read the 'Version:' header in the file comments, or check the theme's version.php file if one exists
    Affected if The version number is 9.5.4 or lower (all versions up to and including 9.5.4 are affected)
  3. Locate the vulnerable et_ajax_required_plugins_popup function
    Search for the function definition in the theme files: grep -r 'function et_ajax_required_plugins_popup' wp-content/themes/xstore/
    Affected if The function exists in the theme code (this function contains the LFI vulnerability)
  4. Verify WordPress user roles are present
    Check WordPress users table: SELECT user_login, meta_key, meta_value FROM wp_usermeta WHERE meta_key = 'wp_capabilities';
    Affected if Any user accounts exist with Subscriber-level or higher role, making exploitation possible if the attacker obtains credentials

You are affected if the XStore theme is active and its version is 9.5.4 or lower, and your site has any subscriber-level or higher user accounts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the XStore theme to a version newer than 9.5.4 when a patch becomes available, or implement input validation/sanitization on the file inclusion parameters in the vulnerable function.

Recommended fix Moderate confidence

XStore theme version 9.5.5 or later

  1. Update the XStore theme to version 9.5.5 or later via WordPress admin dashboard (Appearance > Themes) or via the theme vendor (8theme)
  2. Verify the update was successful by checking the theme version in Appearance > Themes
  3. If using a child theme, ensure it is also updated to be compatible with the parent theme update
  4. Review user accounts and remove any unauthorized Subscriber-level accounts that were not intentionally created
Caveat Minor version updates typically do not include breaking changes, but always review theme changelog before updating production sites

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11746 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11746 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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