ProSolution WP Client vulnerabilities
7 known CVE vulnerabilities in ProSolution WP Client, translated and rated.
- CVE-2026-16098Critical
The ProSolution WP Client plugin for WordPress up to version 2.0.10 contains an arbitrary file upload vulnerability. Missing validation of the Content-Disposition header allows unauthenticated attackers to upload files that may be executable, leading to remote code execution.
- CVE-2026-14524Critical
The ProSolution WP Client plugin for WordPress up to version 2.0.8 contains an arbitrary file deletion vulnerability. Insufficient file path validation in the proSol_fileDeleteProcess function allows unauthenticated attackers to delete arbitrary files on the server, potentially leading to remote code execution.
- CVE-2026-19053Critical
The ProSolution WP Client plugin before version 2.0.6 does not sanitize and escape a parameter before using it in a SQL statement reachable by unauthenticated visitors, leading to a blind SQL injection.
- CVE-2026-6555Critical
The ProSolution WP Client plugin for WordPress up to version 2.0.0 has an arbitrary file upload vulnerability due to array validation mismatch – only the first file is validated, but all are uploaded.
- CVE-2026-19052Medium
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 plugin's activity records.
- CVE-2026-19050Medium
The ProSolution WP Client WordPress plugin before 2.0.9 does not validate a user-supplied URL or check the requester's capability or nonce before making a server-side HTTP request. This allows any authenticated user, such as a subscriber, to make the site issue arbitrary requests to internal hosts and services, including requests with attacker-chosen method, headers, and body.
- CVE-2026-19049High
The ProSolution WP Client plugin before version 2.0.9 does not sanitize a cookie value before using it in SQL queries, and processes that cookie on every request without any authentication or capability check. This allows unauthenticated users to read arbitrary data from the database and to delete the records the plugin stores.

