# CVE-2019-25746: WordPress Sliced Invoices 3.8.2 SQL Injection via post Parameter

> Authenticated attackers can inject SQL via the post parameter in Sliced Invoices to read or modify database information.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-f8m6-3296-2jx2

## What is CVE-2019-25746?

CVE-2019-25746 is a high-severity SQL injection vulnerability in SlicedInvoices Sliced Invoices, published on 15 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

WordPress Sliced Invoices 3.8.2 contains an authenticated SQL injection vulnerability that allows authenticated attackers to manipulate database queries by injecting SQL code through the 'post' parameter. Attackers can send requests to the admin.php endpoint with action=duplicate_quote_invoice and malicious 'post' values to extract sensitive database information or modify data.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2019-25746?


## How do I fix CVE-2019-25746?

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

## Is CVE-2019-25746 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25746 and fix it if it is affected.

What it is: CVE-2019-25746 is a high-severity SQL injection vulnerability in SlicedInvoices Sliced Invoices, published on 15 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25746 exists.

Affected product: SlicedInvoices Sliced Invoices. 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-2019-25746/ (Markdown: https://insights.sbomify.com/CVE-2019-25746/index.md)
```

## Sources

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

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