XStore
xstore · theme
Known security vulnerabilities for XStore. Find out in seconds which version runs on your site with WP Lens.
12 known vulnerabilities
3 critical · 7 exploitable without logging in · 1 with public exploit code · latest Feb 19, 2026
Not in the wordpress.org directory (paid or third-party distribution). We cannot verify its latest release or maintenance status here; fixed-version data comes from the record itself.
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- Critical 9.8
CVE-2024-33561unauthenticated≤ 9.3.8
WordPress XStore theme <= 9.3.8 - Unauthenticated Broken Access Control vulnerability
- Critical 9.3
CVE-2024-33559unauthenticated≤ 9.3.5
WordPress XStore theme <= 9.3.5 - Unauthenticated SQL Injection vulnerability
- Critical 9.0
CVE-2024-33560unauthenticated≤ 9.3.8
WordPress XStore theme <= 9.3.8 - Unauthenticated Local File Inclusion vulnerability
- High 8.8
CVE-2024-33563login required≤ 9.3.8
WordPress XStore theme <= 9.3.8 - Broken Access Control vulnerability
- High 7.5
CVE-2025-64193login required≤ 9.6.1
WordPress XStore theme < 9.6.1 - Local File Inclusion vulnerability
- High 7.1
CVE-2025-64191unauthenticated · needs a click≤ 9.6.1
WordPress XStore theme < 9.6.1 - Cross Site Scripting (XSS) vulnerability
- High 7.1
CVE-2024-33562unauthenticated · needs a click≤ 9.3.5
WordPress XStore theme <= 9.3.5 - Reflected Cross Site Scripting (XSS) vulnerability
- Medium 6.5
CVE-2026-25305login required≤ 9.6.4
WordPress XStore theme <= 9.6.4 - Cross Site Scripting (XSS) vulnerability
- Medium 6.3
CVE-2025-64192login required≤ 9.6
WordPress XStore theme < 9.6 - Broken Access Control vulnerability
- Medium 5.3
CVE-2026-25006unauthenticated≤ 9.6.4
WordPress XStore theme <= 9.6.4 - Arbitrary Shortcode Execution vulnerability
- Medium 5.3
CVE-2025-60100unauthenticated≤ 9.6
WordPress XStore theme < 9.6 - Content Injection vulnerability
- Medium 4.3
CVE-2024-33564login required≤ 9.3.8
WordPress XStore theme <= 9.3.8 - Arbitrary Option Update vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).