The WP Ultimate CSV Importer WordPress plugin before 9.2 does not use a site-specific secret when deriving the storage
Source GCVE Database
Not known to be exploited · CVSS 3.7 Low : upgrade to 9.2 when convenient.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9.2
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 16 Nov 2026.
What to do
Upgrade WP Ultimate CSV Importer to 9.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WP Ultimate CSV Importer | Affected
| Fixed in
|
AI-suggested
A fix is available in version 9.2 of the WP Ultimate CSV Importer plugin. Users should upgrade to version 9.2 or later to ensure that import logs are stored securely with a site-specific secret and that direct access to these logs is blocked.
Description
The WP Ultimate CSV Importer WordPress plugin before 9.2 does not use a site-specific secret when deriving the storage location of the import logs it writes under the uploads directory, nor does it block direct access to them, allowing unauthenticated attackers to retrieve the personal data of users imported from a CSV file.