# CVE-2022-4372: Web Invoice <= 2.1.3 - Authenticated SQLi

> Authenticated SQL injection in Web Invoice plugin allows attackers to manipulate database queries, potentially exposing or modifying data.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jan 2023
- **Updated:** 10 Apr 2025
- **Also known as:** GHSA-q66j-q3q8-gqh8

## What is CVE-2022-4372?

CVE-2022-4372 is a high-severity SQL injection vulnerability in Unknown Web Invoice, published on 2 Jan 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Web Invoice WordPress plugin through 2.1.3 does not properly sanitize and escape a parameter before using it in a SQL statement, leading to a SQL Injection exploitable by high privilege users such as admin by default. However, depending on the plugin configuration, other users, such as subscriber could exploit this as well

## Which versions are affected by CVE-2022-4372?

It affects 1 product.


Products: Web Invoice Project Web Invoice.

## How do I fix CVE-2022-4372?

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

## Is CVE-2022-4372 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4372 and fix it if it is affected.

What it is: CVE-2022-4372 is a high-severity SQL injection vulnerability in Unknown Web Invoice, published on 2 Jan 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4372 exists.

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

## Sources

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

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