# CVE-2022-1182: Visual Slide Box Builder <= 3.2.9 - Subscriber+ SQLi

> Authenticated users can exploit SQL injection in Visual Slide Box Builder to read or modify database contents.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 16 May 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-6xq7-pgjf-qf76

## What is CVE-2022-1182?

CVE-2022-1182 is a high-severity SQL injection vulnerability in Unknown Visual Slide Box Builder, published on 16 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Visual Slide Box Builder WordPress plugin through 3.2.9 does not sanitise and escape various parameters before using them in SQL statements via some of its AJAX actions available to any authenticated users (such as subscriber), leading to SQL Injections

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

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

It affects 1 product.


Products: Visual Slide Box Builder Project Visual Slide Box Builder.

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

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

## Is CVE-2022-1182 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-1182 is a high-severity SQL injection vulnerability in Unknown Visual Slide Box Builder, published on 16 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-1182 in the wild and no public exploit code.

Affected product: Unknown Visual Slide Box Builder. 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-1182/ (Markdown: https://insights.sbomify.com/CVE-2022-1182/index.md)
```

## Sources

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

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