# CVE-2026-2343: PeproDev Ultimate Invoice <= 2.2.5 - Unauthenticated Invoice Archive Download

> Attackers can brute force predictable ZIP filenames to download unauthenticated invoice archives containing sensitive PII.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Mar 2026
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-w7c9-8pqp-97mg

## What is CVE-2026-2343?

CVE-2026-2343 is a medium-severity vulnerability in Unknown PeproDev Ultimate Invoice, published on 25 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The PeproDev Ultimate Invoice WordPress plugin through 2.2.5 has a bulk download invoices action that generates ZIP archives containing exported invoice PDFs. The ZIP files are named predictably making it possible to brute force and retreive PII.

## Which versions are affected by CVE-2026-2343?


## How do I fix CVE-2026-2343?

No fix has been published for CVE-2026-2343 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-2343 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2343 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2343 and fix it if it is affected.

What it is: CVE-2026-2343 is a medium-severity vulnerability in Unknown PeproDev Ultimate Invoice, published on 25 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2343 exists.

Affected product: Unknown PeproDev Ultimate Invoice. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-2343/ (Markdown: https://insights.sbomify.com/CVE-2026-2343/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-2343
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2343
- OSV: https://osv.dev/vulnerability/CVE-2026-2343

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-2343/
Summaries are generated and may contain mistakes; the official description above is the record.