# CVE-2024-13719: PeproDev Ultimate Invoice <= 2.0.9 - Insecure Direct Object Reference to Unauthenticated Order Information Exposure

> Unauthenticated attackers can view sensitive invoice data containing user PII due to missing validation in the PeproDev Ultimate Invoice plugin.

- **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:** 19 Feb 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-c7vr-vpm2-822g

## What is CVE-2024-13719?

CVE-2024-13719 is a medium-severity vulnerability in PeproDev Ultimate Invoice, published on 19 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The PeproDev Ultimate Invoice plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.0.9 via the invoicing viewer due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to view invoices for completed orders which can contain PII of users.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2024-13719?

It affects 1 product.


Products: Pepro Peprodev Ultimate Invoice.

## How do I fix CVE-2024-13719?

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

## Is CVE-2024-13719 being exploited?

There is no known exploitation of CVE-2024-13719 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-13719 and fix it if it is affected.

What it is: CVE-2024-13719 is a medium-severity vulnerability in PeproDev Ultimate Invoice, published on 19 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-13719 in the wild and no public exploit code.

Affected product: 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-2024-13719/ (Markdown: https://insights.sbomify.com/CVE-2024-13719/index.md)
```

## Sources

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

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