WordPress XStore theme < 9.6 - Content Injection vulnerability

published 2025-09-26 last yr. modified 2026-10-11 29d ago also EUVD-2025-31300

cvss: 5.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 21%
public exploits: 0; none known

Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) vulnerability in 8theme XStore xstore allows Code Injection.This issue affects XStore: from n/a through < 9.6.

Patch / fix

fixed in 1

8theme XStore 9.6

Is CVE-2025-60100 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: last yr. (2025-09-29)

Exploit prediction

0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected products

8theme XStore

Classification

Weakness

CWE-80 Improper Neutralization of Script-Related HTML Tags in a Web Page

Technology feeds

WordPress rss critical rss

References

patchstack.com /database/Wordpress/Theme/xstore/vulnerability/wordpress-xstore-theme-9-5-3-content-injection-vulnerability?_s
vdb-entry

Sources

CVE List CVE-2025-60100
NVD CVE-2025-60100

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.

json all entries feed