# CVE-2026-7842: Infility Global < 2.15.20 - Editor+ SQL Injection via orderby Parameter

> Authenticated editors can perform blind SQL injection to extract database data if the ImportData module is enabled.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-jgxx-4fc8-ff8f

## What is CVE-2026-7842?

CVE-2026-7842 is a medium-severity SQL injection vulnerability in Unknown Infility Global, published on 23 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Infility Global Infility Global WordPress plugin before 2.15.20 for WordPress does not sanitize or validate the orderby and order parameters in the import_list(), url_detail(), and file_detail() admin page callbacks before using them in SQL queries, allowing authenticated attackers with Editor-level access or higher to perform time-based blind SQL injection and extract sensitive data from the database. The ImportData module must be enabled via the Infility Global WordPress plugin before 2.15.20's module toggle page.

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


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

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

## Is CVE-2026-7842 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7842 is a medium-severity SQL injection vulnerability in Unknown Infility Global, published on 23 Jun 2026. 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-2026-7842 exists.

Affected product: Unknown Infility Global. 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-7842/ (Markdown: https://insights.sbomify.com/CVE-2026-7842/index.md)
```

## Sources

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

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