# CVE-2023-0263: WP Yelp Review Slider < 7.1 - Subscriber+ SQLi

> A SQL injection vulnerability in the WP Yelp Review Slider plugin allows subscribers to manipulate database queries, potentially exposing or altering data.

- **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:** 13 Feb 2023
- **Updated:** 21 Mar 2025
- **Also known as:** GHSA-g7p8-vcmx-9h8r

## What is CVE-2023-0263?

CVE-2023-0263 is a high-severity SQL injection vulnerability in Unknown WP Yelp Review Slider, published on 13 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WP Yelp Review Slider WordPress plugin before 7.1 does not properly sanitise and escape a parameter before using it in a SQL statement, leading to a SQL injection exploitable by users with a role as low as subscriber.

## Which versions are affected by CVE-2023-0263?

It affects 1 product.


Products: Ljapps Wp Yelp Review Slider.

## How do I fix CVE-2023-0263?

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

## Is CVE-2023-0263 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-0263 and fix it if it is affected.

What it is: CVE-2023-0263 is a high-severity SQL injection vulnerability in Unknown WP Yelp Review Slider, published on 13 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-0263 exists.

Affected product: Unknown WP Yelp Review Slider. 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-2023-0263/ (Markdown: https://insights.sbomify.com/CVE-2023-0263/index.md)
```

## Sources

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

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