# CVE-2026-19052: ProSolution WP Client < 2.0.9 - Subscriber+ proSol_ajaxTablesync and proSol_ajaxClearlog Calls

> Authenticated users can trigger administrative data synchronization and clear activity logs due to missing capability checks in the ProSolution WP Client plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:** 12 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-98wq-55q3-fr94

## What is CVE-2026-19052?

CVE-2026-19052 is a medium-severity missing authorization vulnerability in Unknown ProSolution WP Client, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The ProSolution WP Client WordPress plugin before 2.0.9 does not perform capability checks on two administrative AJAX actions, and the nonce they rely on is published on its public frontend, allowing any authenticated user, such as a subscriber, to trigger an administrative data synchronisation and to clear the ProSolution WP Client WordPress plugin before 2.0.9's activity records.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-19052?


## How do I fix CVE-2026-19052?

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

## Is CVE-2026-19052 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19052 and fix it if it is affected.

What it is: CVE-2026-19052 is a medium-severity missing authorization vulnerability in Unknown ProSolution WP Client, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19052 in the wild and no public exploit code.

Affected product: Unknown ProSolution WP Client. 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-2026-19052/ (Markdown: https://insights.sbomify.com/CVE-2026-19052/index.md)
```

## Sources

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

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