# CVE-2023-4374: WP Remote Users Sync <= 1.2.11 - Missing Authorization to Authenticated (Subscriber+) Log View

> Authenticated subscribers can view logs due to missing capability checks in the WP Remote Users Sync plugin.

- **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:** 16 Aug 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-q5x2-6r32-h345

## What is CVE-2023-4374?

CVE-2023-4374 is a medium-severity missing authorization vulnerability in frogerme WP Remote Users Sync, published on 16 Aug 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WP Remote Users Sync plugin for WordPress is vulnerable to unauthorized access of data and addition of data due to a missing capability check on the 'refresh_logs_async' functions in versions up to, and including, 1.2.11. This makes it possible for authenticated attackers with subscriber privileges or above, to view logs.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Froger Wp Remote Users Sync.

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

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

## Is CVE-2023-4374 being exploited?

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

## Other vulnerabilities in frogerme WP Remote Users Sync

- [CVE-2023-3958](https://insights.sbomify.com/CVE-2023-3958/): WP Remote Users Sync <= 1.2.12 - Authenticated (Subscriber+) Server Side Request Forgery (high 8.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-4374 is a medium-severity missing authorization vulnerability in frogerme WP Remote Users Sync, published on 16 Aug 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-4374 in the wild and no public exploit code.

Affected product: frogerme WP Remote Users Sync. 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-4374/ (Markdown: https://insights.sbomify.com/CVE-2023-4374/index.md)
```

## Sources

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

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