# CVE-2022-22735: Simple Quotation <= 1.3.2 - Subscriber+ SQL injection

> Authenticated users can perform SQL injection attacks in the Simple Quotation WordPress plugin due to missing authorization and improper data escaping.

- **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:** 14 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-533j-r4h4-5hxg

## What is CVE-2022-22735?

CVE-2022-22735 is a high-severity SQL injection vulnerability in Unknown Simple Quotation, published on 14 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Simple Quotation WordPress plugin through 1.3.2 does not have authorisation (and CSRF) checks in various of its AJAX actions and is lacking escaping of user data when using it in SQL statements, allowing any authenticated users, such as subscriber to perform SQL injection attacks

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

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

It affects 1 product.


Products: Sedlex Simple Quotation.

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

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

## Is CVE-2022-22735 being exploited?

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

## Other vulnerabilities in Unknown Simple Quotation

- [CVE-2022-22734](https://insights.sbomify.com/CVE-2022-22734/): Simple Quotation <= 1.3.2 - Quote Creation/Edition via CSRF to Stored Cross-Site Scripting (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-22735 is a high-severity SQL injection vulnerability in Unknown Simple Quotation, published on 14 Mar 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-22735 in the wild and no public exploit code.

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

## Sources

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

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