# CVE-2024-48043: WordPress ShortPixel Image Optimizer plugin <= 5.6.3 - SQL Injection vulnerability

> Attackers can perform blind SQL injection to read database data via the ShortPixel Image Optimizer plugin.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Oct 2024
- **Updated:** 12 May 2026
- **Also known as:** GHSA-g487-gqfx-jgg8

## What is CVE-2024-48043?

CVE-2024-48043 is a high-severity SQL injection vulnerability in ShortPixel Image Optimizer, published on 17 Oct 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in ShortPixel ShortPixel Image Optimizer shortpixel-image-optimiser allows Blind SQL Injection.This issue affects ShortPixel Image Optimizer: from n/a through <= 5.6.3.

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

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


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

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

## Is CVE-2024-48043 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-48043 is a high-severity SQL injection vulnerability in ShortPixel Image Optimizer, published on 17 Oct 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-48043 in the wild and no public exploit code.

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

## Sources

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

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