Ever Accounting < 2.3.3 - Accounting Manager+ Arbitrary File Deletion via CSV Import
- Exploited
- No known exploitation
- Fix
- Fixed in 2.3.3
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.3.3.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.15% · 4th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 12/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
The Ever Accounting WordPress plugin lets a user with the Accounting Manager role delete arbitrary files on the server, such as wp-config.php, which can take the entire site offline. The flaw is in the CSV import routine, which does not restrict the supplied file path to an allowed directory.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
The Ever Accounting WordPress plugin before 2.3.3 does not restrict the file path supplied to its CSV import routine to an allowed directory, allowing users with its custom Accounting Manager role (which does not have administrator privileges) to delete arbitrary files on the server, such as wp-config.php, which takes the entire site offline.
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.3.3.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Unknown Ever Accounting
fixed in 2.3.3
Evidence 1
- Exploit
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-118045
Is CVE-2026-118045 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-118045?
Ever Accounting: before 2.3.3.Source: cve.now feed data
How do I fix CVE-2026-118045?
Upgrade to a fixed version: 2.3.3.Source: cve.now feed data