# CVE-2021-38324: SP Rental Manager <= 1.5.3 Unauthenticated SQL Injection

> Unauthenticated attackers can exploit SQL injection in SP Rental Manager to retrieve sensitive database information.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Sep 2021
- **Updated:** 5 May 2025
- **Also known as:** GHSA-w3vx-7cpg-r478

## What is CVE-2021-38324?

CVE-2021-38324 is a high-severity SQL injection vulnerability in SP Rental Manager, published on 9 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The SP Rental Manager WordPress plugin is vulnerable to SQL Injection via the orderby parameter found in the ~/user/shortcodes.php file which allows attackers to retrieve information contained in a site's database, in versions up to and including 1.5.3.

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

## Which versions are affected by CVE-2021-38324?

It affects 1 product.


Products: Smartypantsplugins Sp Rental Manager.

## How do I fix CVE-2021-38324?

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

## Is CVE-2021-38324 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-38324 and fix it if it is affected.

What it is: CVE-2021-38324 is a high-severity SQL injection vulnerability in SP Rental Manager, published on 9 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-38324 in the wild and no public exploit code.

Affected product: SP Rental Manager. 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-2021-38324/ (Markdown: https://insights.sbomify.com/CVE-2021-38324/index.md)
```

## Sources

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

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