ProSolution WP Client lets Subscribers run administrative actions
ProSolution WP Client before 2.0.9 exposes the authenticated AJAX actions proSol_ajaxTablesync and proSol_ajaxClearlog without capability checks, while publishing their prosolwpclient nonce on the public front end. A Subscriber can submit table, synctype and batch to trigger administrative data synchronization or cleartype to clear activity records through proSol_clearLog(). The synchronized datasets and clear-log scope depend on configuration.
- Component
- ProSolution WP Client
- Plugin slug
prosolution-wp-client- Affected
- < 2.0.9
- Safe version
2.0.9- Published
- Aug 12, 2026
- Weakness
- CWE-862 — Missing Authorization
This CVE was published Aug 12, 2026 and is one of 10 known issues for this plugin.
Update, patch or deactivate.
Update to 2.0.9 or later. Review low-privilege AJAX traffic, verify synchronized data, and investigate missing activity records.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical 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.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N