CVE-2022-2669: WP Taxonomy Import · Cross-Site Scripting (XSS)
Affects WP Taxonomy ImportSource CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Sep 2022
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Unknown WP Taxonomy Import | Affected
| Fixed in– |
AI-suggested
European organizations should immediately audit their WordPress installations to identify the presence of the WP Taxonomy Import plugin version 1.0.4 or earlier. If found, they should upgrade to a patched version once available or remove the plugin if it is not essential. In the absence of an official patch, organizations can implement web application firewall (WAF) rules to detect and block typical XSS payloads targeting the vulnerable parameter. Additionally, input validation and output encoding should be enforced at the application level if custom development is possible. Organizations should also educate users and administrators about the risks of clicking suspicious links and implement Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts. Regular security scanning and monitoring for unusual activity related to WordPress sites can help detect exploitation attempts early. Finally, maintaining updated backups and incident response plans will aid in recovery if exploitation occurs.
Description
The WP Taxonomy Import WordPress plugin through 1.0.4 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting