# CVE-2023-4686: WP Customer Reviews <= 3.6.6 - Authenticated (Subscriber+) Sensitive Information Exposure

> Authenticated attackers can extract sensitive data from protected and trashed posts via the ajax_enabled_posts function in WP Customer Reviews.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 22 Nov 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-q9mg-8x46-h8mx

## What is CVE-2023-4686?

CVE-2023-4686 is a medium-severity vulnerability in bompus WP Customer Reviews, published on 22 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WP Customer Reviews plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 3.6.6 via the ajax_enabled_posts function. This can allow authenticated attackers to extract sensitive data such as post titles and slugs, including those of protected and trashed posts and pages in addition to other post types such as galleries.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Gowebsolutions Wp Customer Reviews.

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

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

## Is CVE-2023-4686 being exploited?

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

## Other vulnerabilities in bompus WP Customer Reviews

- [CVE-2016-10902](https://insights.sbomify.com/CVE-2016-10902/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2021-24135](https://insights.sbomify.com/CVE-2021-24135/): WP Customer Reviews < 3.4.3 - Multiple Unauthenticated and Low Priv Authenticated Stored XSS (medium 6.1)
- [CVE-2016-10901](https://insights.sbomify.com/CVE-2016-10901/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2024-1849](https://insights.sbomify.com/CVE-2024-1849/): WP Customer Reviews < 3.7.1 - Malicious Redirect via HTTP-EQUIV Injection (medium 5.4)
- [CVE-2021-24296](https://insights.sbomify.com/CVE-2021-24296/): WP Customer Reviews < 3.5.6 - Authenticated Stored Cross-Site Scripting (XSS) (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-4686 is a medium-severity vulnerability in bompus WP Customer Reviews, published on 22 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-4686 in the wild and no public exploit code.

Affected product: bompus WP Customer Reviews. 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-4686/ (Markdown: https://insights.sbomify.com/CVE-2023-4686/index.md)
```

## Sources

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

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