The Ever Accounting WordPress plugin before 2.3.3 does not restrict the file path supplied to its CSV import routine
Source GCVE Database
Not known to be exploited : upgrade to 2.3.3 soon.
Data as of 6 Nov 2026, 07:32 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 2.3.3
Exploitation evidence
Disclosed: evidence found.
CVE published 6 Nov 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 5 Nov 2026.
What to do
Upgrade Ever Accounting (WordPress plugin) to 2.3.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Ever Accounting | Affected
| Fixed in
|
AI-suggested
Upgrade the Ever Accounting WordPress plugin to version 2.3.3 or later, where this vulnerability has been addressed by restricting file paths in the CSV import routine. If you cannot patch yet, restrict the Accounting Manager role's access or disable the CSV import feature to prevent exploitation.
Description
The Ever Accounting WordPress plugin versions before 2.3.3 contain a vulnerability in the CSV import routine that fails to restrict file paths to an allowed directory. This flaw allows users with the custom Accounting Manager role, which lacks administrator privileges, to delete arbitrary files on the server, including critical files like wp-config.php, potentially taking the entire site offline.