Reported vulnerability

XStore < 9.6 - Unauthenticated Arbitrary Shortcode Execution

Q: Which versions of XStore are affected?

Wordfence lists these affected versions: Start version unspecified, before 9.6. Use the version checker above to compare your installed release with this report.

Q: Is a fix available for XStore?

Wordfence reports a fix for this issue in XStore. It lists these fixed versions: 9.6. Back up your website and test the recommended update before applying it to your live site.

Q: Where can I find my installed theme version?

In WordPress, go to Appearance > Themes and open Theme Details to find the installed version.

Published 26 Sept 2025

Updated 17 Mar 2026

CVE-2025-60100

Compare your installed software with the affected versions below. Follow the source’s remediation guidance and test an available update after taking a backup. A database entry describes a reported issue; it does not establish whether a particular website has been compromised.

Does this affect my version?

Check your installed version against this advisory. This compares the report’s version ranges and does not scan your website.

Wordfence advisory

medium · CVSS 6.5

The The XStore theme for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and excluding, 9.6. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes.

Severity vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

XStore

Software: theme · xstore
Affected versions: Start version unspecified, before 9.6
Fix availability: Fix available
Fixed versions: 9.6

Recommended action

Update to version 9.6, or a newer patched version

Further references (1)

wordfence.com/threat-intel/vulnerabilities/id/73897594-d25c-410e-81b1-70b6a8136aee?source=api-prod

Data sources and licences

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

Read licence terms

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

Read licence terms

Source: Wordfence

Need help fixing this issue?

Get help checking your site, applying an available update and resolving any problems after updating.

Get help with this issue

Questions about this vulnerability

Which versions of XStore are affected?

Wordfence lists these affected versions: Start version unspecified, before 9.6. Use the version checker above to compare your installed release with this report.

Is a fix available for XStore?

Wordfence reports a fix for this issue in XStore. It lists these fixed versions: 9.6. Back up your website and test the recommended update before applying it to your live site.

Where can I find my installed theme version?

In WordPress, go to Appearance > Themes and open Theme Details to find the installed version.

Does an affected version mean my website has been hacked?

An affected version means the installed release matches a vulnerability described in this report. It does not show whether anyone has exploited it on your website. The checker compares version numbers with stored reports; it does not inspect your website.

These reports cover at least one of the same plugins, themes or WordPress core. Check each report’s affected versions separately.

Back to vulnerability database